CVE-2026-6609 | liangliangyy DjangoBlog up to 2.1.0.0 oauth/views.py form_valid oauthid improper authorization

VDB-358244 · SUBMIT #790288 · CVE-2026-6609 LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 OAUTH/VIEWS.PY FORM_VALID OAUTHID IMPROPER AUTHORIZATION HISTORYDIFFRELATEJSONXMLCTI Summaryinfo A vulnerability described as critical has been identified in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is the function form_valid of the file oauth/views.py. Such manipulation of the argument oauthid leads to improper authorization. This vulnerability is traded as CVE-2026-6609. 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. It has been rated as critical. Affected by this issue is the function form_valid of the file oauth/views.py. The manipulation of the argument oauthid with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-6609. The exploitation is known to be easy. The attack may be launched remotely. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1548.002. 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.3 VulDB Meta Temp Score: 5.7 VulDB Base Score: 6.3 VulDB Temp Score: 5.7 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: Improper authorization CWE: CWE-285 / CWE-266 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-6609 (🔒) GCVE (CVE): GCVE-0-2026-6609 GCVE (VulDB): GCVE-100-358244 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/19/2026 18:11 Changes: 04/19/2026 18:11 (58) Complete: 🔍 Submitter: Dem0 Cache ID: 99:D8E:101 Submitinfo Accepted Submit #790288: liangliangyy DjangoBlog <= 2.1.0.0 Insecure Direct Object Reference (by Dem0) Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸