CVE-2026-6610 | liangliangyy DjangoBlog up to 2.1.0.0 Setting djangoblog/settings.py USER/PASSWORD hard-coded credentials

VDB-358245 · SUBMIT #790289 · CVE-2026-6610 LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 SETTING DJANGOBLOG/SETTINGS.PY USER/PASSWORD HARD-CODED CREDENTIALS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 3.4 $0-$5k 1.82 Summaryinfo A vulnerability classified as critical has been found in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component Setting Handler. Performing a manipulation of the argument USER/PASSWORD results in hard-coded credentials. This vulnerability is known as CVE-2026-6610. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way. Detailsinfo A vulnerability classified as problematic has been found in liangliangyy DjangoBlog up to 2.1.0.0. This affects some unknown processing of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument USER/PASSWORD with an unknown input leads to a hard-coded credentials vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-6610. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1110.001 for this issue. The exploit is shared for download 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: 3.7 VulDB Meta Temp Score: 3.4 VulDB Base Score: 3.7 VulDB Temp Score: 3.4 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-6610 (🔒) GCVE (CVE): GCVE-0-2026-6610 GCVE (VulDB): GCVE-100-358245 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/19/2026 18:11 Changes: 04/19/2026 18:11 (58) Complete: 🔍 Submitter: Dem0 Cache ID: 99:BE3:101 Submitinfo Accepted Submit #790289: liangliangyy DjangoBlog <= 2.1.0.0 Security Misconfiguration + Hardcoded Credentials (by Dem0) Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸