CVE-2026-6580 affects DjangoBlog versions up to 2.1.0.0 and involves improper handling of the Amap API Call Handler in the owntracks/views.py component, specifically related to manipulation of the key argument that leads to use of a hard-coded cryptographic key. This vulnerability enables attackers to potentially compromise the confidentiality, integrity, and availability of affected systems. The vulnerability carries a CVSS 3.1 score of 7.3 (HIGH), with a network-based attack vector requiring no authentication or user interaction, making it relatively easy to exploit remotely. The impact is moderate, affecting confidentiality, integrity, and availability of the application. Public exploit code is available, and the vulnerability has been actively disclosed despite the vendor's lack of response to early notification. While the EPSS score of 0.000380 suggests limited real-world exploitation activity currently, the active presence on threat tracking lists and public disclosure of exploit details warrant immediate patching, particularly for internet-facing DjangoBlog installations.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
| Liangliangyy | DjangoBlog | 2.1.0CNA affected |
CVSS version used by this source: 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.1 Bluesky, 0.1 Mastodon, and 0.4 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.