CVE-2026-93456

django-page-cms through 2.0.13 CSRF via admin mutation views

Published Sep 18, 2026 CVSS 4.0 · 8.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

django-page-cms versions up to 2.0.13 mistakenly exclude five admin mutation views from CSRF protection. This omission allows an attacker to forge requests that modify page content without needing a CSRF token. The attacker can trick any signed‑in editor into visiting a malicious page, causing the editor to unknowingly submit a request that stores unescaped content. That stored content then renders for all site visitors, delivering stored cross‑site scripting attacks that can execute arbitrary JavaScript on the client side.

Affected Systems

The vulnerability affects the Django (Python) CMS package "django-page-cms" from publisher batiste, impacting all releases through version 2.0.13 inclusive. Administrators using any of these versions exposed to the admin mutation views are at risk.

Risk and Exploitability

The CVSS score of 8.4 identifies this flaw as high severity. The EPSS score of < 1% indicates that, at the time of analysis, the likelihood of exploitation is low, and it is not currently listed in the CISA KEV catalog. However, the exploit requires the attacker to lure a legitimate editor to a malicious page, forcing a forged request to alter page content. Once successful, all site visitors are exposed to injected scripts, compromising confidentiality and integrity of the site’s content. Attack vectors rely on user interaction, HTTP request forging, and the presence of an authenticated session.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade django-page-cms to a release that restores CS newer than 2.0.13).
  • Verify that Django’s CSRF middleware is active and that all admin URLs require CSRF token validation before processing mutations.
  • As a temporary protective measure, limit admin account access to trusted IP ranges or enable two‑factor authentication to reduce the chance of credential compromise.

Generated by OpenCVE AI on September 19, 2026 at 21:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

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

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N'}

cvssV4_0

{'score': 8.4, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:23 PM
Reserved
Sep 17, 2026, 11:37 PM
Status
Deferred
Published
Sep 18, 2026, 2:17 AM
Modified
Sep 22, 2026, 8:53 PM