Missing Authentication in DjangoBlog by liangliangyy
CVE-2026-6577

6.9MEDIUM

Key Information:

Vendor

Liangliangyy

Status
Djangoblog
Vendor
CVE Published:
19 April 2026

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2026-6577?

A notable vulnerability exists in DjangoBlog by liangliangyy, impacting versions up to 2.1.0.0. This flaw resides within an undisclosed function in the logtracks Endpoint (owntracks/views.py), resulting in a lack of necessary authentication measures. As a result, unauthorized users can potentially exploit this weakness remotely. The exploit for this vulnerability has been made publicly available. Despite early notification attempts, the vendor has not responded to the disclosure.

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-6577 - Proof of Concept

References

https://vuldb.com/vuln/358212
vdb-entry
https://vuldb.com/vuln/358212/cti
signaturepermissions-required
https://vuldb.com/submit/790282
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
.