CVE-2026-6579 is an authentication bypass vulnerability affecting liangliangyy DjangoBlog versions up to 2.1.0.0, specifically in the Clean Endpoint function of the blog/views.py component. The flaw allows unauthenticated access to an unknown function within the application, enabling remote exploitation without any user interaction required. The vendor has been notified but has not provided a response or patch. The vulnerability carries a CVSS score of 6.5 (Medium severity) with a network-based attack vector and low complexity, requiring no privileges or user interaction. The impact is limited to integrity and availability degradation, though confidentiality is not affected. This profile indicates a moderate but actionable risk that could allow attackers to modify or disrupt service availability. The exploit has been publicly disclosed and is available to potential attackers. While the vulnerability is listed as active on threat tracking systems and has a moderate FAUCET risk score of 44.0, it is not currently included in the Known Exploited Vulnerabilities (KEV) catalog, suggesting it has not yet seen widespread active exploitation in the wild. Organizations running affected DjangoBlog versions should prioritize assessment and mitigation to prevent unauthorized access.
| 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:N/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.0 Mastodon, and 0.4 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.