CVE-2026-6579 | liangliangyy DjangoBlog up to 2.1.0.0 Clean Endpoint blog/views.py missing authentication
VulDBArchived Apr 19, 2026✓ Full text saved
A vulnerability identified as critical has been detected in liangliangyy DjangoBlog up to 2.1.0.0 . This impacts an unknown function of the file blog/views.py of the component Clean Endpoint . This manipulation causes missing authentication. This vulnerability appears as CVE-2026-6579 . The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358214 · SUBMIT #790286 · CVE-2026-6579
LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 CLEAN ENDPOINT BLOG/VIEWS.PY MISSING AUTHENTICATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.9 $0-$5k 2.54+
Summaryinfo
A vulnerability labeled as critical has been found in liangliangyy DjangoBlog up to 2.1.0.0. Affected is an unknown function of the file blog/views.py of the component Clean Endpoint. Such manipulation leads to missing authentication. This vulnerability is traded as CVE-2026-6579. The attack may be launched remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.
Detailsinfo
A vulnerability was found in liangliangyy DjangoBlog up to 2.1.0.0 and classified as critical. Affected by this issue is an unknown part of the file blog/views.py of the component Clean Endpoint. The manipulation with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is integrity, and availability.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-6579. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Type
Content Management System
Vendor
liangliangyy
Name
DjangoBlog
Version
2.1.0
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9
VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Missing authentication
CWE: CWE-306 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/19/2026 Advisory disclosed
04/19/2026 +0 days VulDB entry created
04/19/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Status: Not defined
CVE: CVE-2026-6579 (🔒)
GCVE (CVE): GCVE-0-2026-6579
GCVE (VulDB): GCVE-100-358214
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 04/19/2026 07:16
Changes: 04/19/2026 07:16 (57)
Complete: 🔍
Submitter: Dem0
Cache ID: 99:9B0:101
Submitinfo
Accepted
Submit #790286: liangliangyy DjangoBlog <= 2.1.0.0 Missing Authentication (by Dem0)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸