liangliangyy DjangoBlog up to 2.1.0.0 oauth/views.py form_valid oauthid improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 3.52 |
Summary
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.
Details
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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23782). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Improper authorizationCWE: 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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/19/2026 Advisory disclosed04/19/2026 VulDB entry created
04/20/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2026-6609 (🔒)
GCVE (CVE): GCVE-0-2026-6609
GCVE (VulDB): GCVE-100-358244
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/19/2026 18:11Updated: 04/20/2026 10:56
Changes: 04/19/2026 18:11 (58), 04/20/2026 10:56 (1)
Complete: 🔍
Submitter: Dem0
Cache ID: 216::103
Submit
Accepted
- Submit #790288: liangliangyy DjangoBlog <= 2.1.0.0 Insecure Direct Object Reference (by Dem0)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.