Vulnerability · Published Apr 19, 2026 · Assigned by VulDB

CVE-2026-6580liangliangyy DjangoBlog Amap API Call views.py hard-coded key

High 7.3

In plain English

A high-severity security flaw in DjangoBlog from liangliangyy. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 21% of all known vulnerabilities).

Severity (CVSS 3.1)7.3High

Exploit odds (30 days)0.3%top 79.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official description

A security vulnerability has been detected in liangliangyy DjangoBlog up to 2.1.0.0. Affected is an unknown function of the file owntracks/views.py of the component Amap API Call Handler. Such manipulation of the argument key leads to use of hard-coded cryptographic key . The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Affected products (as reported)

Vendor	Product	Versions
liangliangyy	DjangoBlog	2.1.0

Weakness: CWE-321, CWE-320 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R

References

VDB-358215 | liangliangyy DjangoBlog Amap API Call views.py hard-coded key vdb-entry, technical-description
VDB-358215 | CTI Indicators (IOB, IOC, TTP, IOA) signature, permissions-required
Submit #790287 | liangliangyy DjangoBlog <= 2.1.0.0 Hardcoded Credentials third-party-advisory
https://github.com/3em0/cve_repo/blob/main/DjangoBlog/Vuln-5-Hardcoded-Amap-API-Key.md exploit