django-page-cms through 2.0.13 CSRF via admin mutation views
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| batiste | django-page-cms | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Batiste | Django-page-cms |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.204% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Batiste
Batiste django-page-cms |
|
| Vendors & Products |
Batiste
Batiste django-page-cms |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | django-page-cms through 2.0.13 exempts five admin mutation views from CSRF protection in pages/admin/views.py, allowing attackers to forge requests that modify page content. Signed-in editors visiting a malicious page can be tricked into storing unescaped content that renders to all visitors, enabling stored cross-site scripting attacks. | |
| Title | django-page-cms through 2.0.13 CSRF via admin mutation views | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|