CVE-2026-6578 | liangliangyy DjangoBlog up to 2.1.0.0 Setting djangoblog/settings.py SECRET_KEY hard-coded credentials

VDB-358213 · SUBMIT #790283 · CVE-2026-6578 LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 SETTING DJANGOBLOG/SETTINGS.PY SECRET_KEY HARD-CODED CREDENTIALS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 2.70+ Summaryinfo A vulnerability identified as critical has been detected in liangliangyy DjangoBlog up to 2.1.0.0. This impacts an unknown function of the file djangoblog/settings.py of the component Setting Handler. This manipulation of the argument SECRET_KEY causes hard-coded credentials. This vulnerability appears as CVE-2026-6578. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way. Detailsinfo A vulnerability has been found in liangliangyy DjangoBlog up to 2.1.0.0 and classified as critical. Affected by this vulnerability is some unknown functionality of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument SECRET_KEY with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. The advisory is shared at github.com. This vulnerability is known as CVE-2026-6578. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1110.001 for this issue. It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Type Content Management System Vendor liangliangyy Name DjangoBlog Version 2.1.0 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.6 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.6 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Hard-coded credentials CWE: CWE-798 / CWE-259 / CWE-255 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/19/2026 Advisory disclosed 04/19/2026 +0 days VulDB entry created 04/19/2026 +0 days VulDB entry last update Sourcesinfo Advisory: github.com Status: Not defined CVE: CVE-2026-6578 (🔒) GCVE (CVE): GCVE-0-2026-6578 GCVE (VulDB): GCVE-100-358213 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/19/2026 07:16 Changes: 04/19/2026 07:16 (58) Complete: 🔍 Submitter: Dem0 Cache ID: 99:72A:101 Submitinfo Accepted Submit #790283: liangliangyy DjangoBlog Hardcoded Credentials Hardcoded Credentials (by Dem0) Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸