liangliangyy DjangoBlog views.py form_valid improper authorization
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| liangliangyy | DjangoBlog | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Liangliangyy | Djangoblog |
|
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.206% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Liangliangyy
Liangliangyy djangoblog |
|
| Vendors & Products |
Liangliangyy
Liangliangyy djangoblog |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw has been found in liangliangyy DjangoBlog up to 2.1.0.0. The affected element is the function form_valid of the file oauth/views.py. This manipulation of the argument oauthid causes improper authorization. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way. | |
| Title | liangliangyy DjangoBlog views.py form_valid improper authorization | |
| Weaknesses | CWE-266 CWE-285 |
|
| References |
| |
| Metrics |
cvssV2_0
|