CVE-2026-6611 | liangliangyy DjangoBlog up to 2.1.0.0 File Upload Endpoint djangoblog/settings.py SECRET_KEY hard-coded key

VDB-358246 · SUBMIT #790313 · CVE-2026-6611 LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 FILE UPLOAD ENDPOINT DJANGOBLOG/SETTINGS.PY SECRET_KEY HARD-CODED KEY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 2.8 $0-$5k 2.50 Summaryinfo A vulnerability classified as problematic was found in liangliangyy DjangoBlog up to 2.1.0.0. This impacts an unknown function of the file djangoblog/settings.py of the component File Upload Endpoint. Executing a manipulation of the argument SECRET_KEY can lead to hard-coded key. This vulnerability is handled as CVE-2026-6611. The attack can be executed remotely. Additionally, an exploit exists. The vendor was contacted early about this disclosure but did not respond in any way. Detailsinfo A vulnerability classified as problematic was found in liangliangyy DjangoBlog up to 2.1.0.0. This vulnerability affects an unknown function of the file djangoblog/settings.py of the component File Upload Endpoint. The manipulation of the argument SECRET_KEY with an unknown input leads to a hard-coded key vulnerability. The CWE definition for the vulnerability is CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. As an impact it is known to affect confidentiality. The advisory is available at github.com. This vulnerability was named CVE-2026-6611. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project. 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: 3.1 VulDB Meta Temp Score: 2.8 VulDB Base Score: 3.1 VulDB Temp Score: 2.8 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 key CWE: CWE-321 / CWE-320 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-6611 (🔒) GCVE (CVE): GCVE-0-2026-6611 GCVE (VulDB): GCVE-100-358246 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:287:101 Submitinfo Accepted Submit #790313: liangliangyy DjangoBlog <= 2.1.0.0 Security Misconfiguration + Hardcoded Credentials (by Dem0) Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸