DjangoBlog Amap API Call Handler Vulnerability in Liangliangyy Software
CVE-2026-6580

6.9MEDIUM

Key Information:

Vendor

Liangliangyy

Status
Djangoblog
Vendor
CVE Published:
19 April 2026

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2026-6580?

A security vulnerability has been identified in Liangliangyy's DjangoBlog, specifically within the Amap API Call Handler. An unknown function in the file owntracks/views.py improperly handles input parameters, allowing the use of hard-coded cryptographic keys. This vulnerability can be exploited remotely, posing a significant threat to data security. Public disclosure of the exploit raises concerns about its potential use, particularly as the vendor has not responded to early warnings regarding this issue.

Affected Version(s)

DjangoBlog 2.1.0

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2026-6580 - Proof of Concept

References

https://vuldb.com/vuln/358215
vdb-entrytechnical-description
https://vuldb.com/vuln/358215/cti
signaturepermissions-required
https://vuldb.com/submit/790287
third-party-advisory

CVSS V4

Score:
6.9
Severity:
MEDIUM
Confidentiality:
Low
Integrity:
Low
Availability:
Low
Attack Vector:
Network
Attack Complexity:
Low
Attack Required:
None
Privileges Required:
Undefined
User Interaction:
None

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

Dem0 (VulDB User)
VulDB CNA Team
.