CVE-2026-6580 | liangliangyy DjangoBlog up to 2.1.0.0 Amap API Call owntracks/views.py key hard-coded key

VDB-358215 · SUBMIT #790287 · CVE-2026-6580 LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 AMAP API CALL OWNTRACKS/VIEWS.PY KEY HARD-CODED KEY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.6 $0-$5k 2.38+ Summaryinfo A vulnerability marked as critical has been reported in liangliangyy DjangoBlog up to 2.1.0.0. Affected by this vulnerability is an unknown functionality of the file owntracks/views.py of the component Amap API Call Handler. Performing a manipulation of the argument key results in hard-coded key. This vulnerability is known as CVE-2026-6580. 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 was found in liangliangyy DjangoBlog up to 2.1.0.0. It has been classified as critical. This affects an unknown code of the file owntracks/views.py of the component Amap API Call Handler. The manipulation of the argument key with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality, integrity, and availability. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-6580. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK. 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: 7.3 VulDB Meta Temp Score: 6.6 VulDB Base Score: 7.3 VulDB Temp Score: 6.6 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-6580 (🔒) GCVE (CVE): GCVE-0-2026-6580 GCVE (VulDB): GCVE-100-358215 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:7D5:101 Submitinfo Accepted Submit #790287: liangliangyy DjangoBlog <= 2.1.0.0 Hardcoded Credentials (by Dem0) Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸