/

CVE-2026-93456

Severity:

HIGH RISK

(8.2)

CSRF (CWE-352) in django-page-cms Admin Mutation Views

CVE-2026-93456

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Stored Cross-Site Scripting and Unauthorized Content Modification

Severity:

HIGH RISK

(8.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

django-page-cms fails to apply CSRF protection to several administrative mutation views, allowing forged requests from a malicious page visited by a signed-in editor.

An attacker may use this weakness to alter page content and store unescaped material that can execute as cross-site scripting when other visitors view the affected page.

Affected context

The vulnerability occurs in django-page-cms administrative views that change page content but are exempt from CSRF protection. It becomes risky when an authenticated editor can access the administration interface and is likely to browse attacker-controlled content while an active session remains available.

Exploit preconditions

  • Attack surface: Administrative page-mutation endpoints
  • Required access: A signed-in editor or other user authorized to modify page content
  • Trigger point: The victim visits a malicious page while an authenticated session is active
  • Why exploitation is possible: The affected views accept state-changing requests without requiring a valid CSRF token, allowing a browser to submit an unauthorized content modification

Why this happens

The underlying bug is an incomplete CSRF protection boundary around state-changing administrative views. By exempting mutation endpoints from Django's CSRF validation, the application trusts browser requests based primarily on the user's existing session, even when those requests originated from an unrelated site. This maps to CWE-352: Cross-Site Request Forgery, and the resulting content change can create a secondary stored cross-site scripting condition when submitted content is not safely escaped or sanitized.

Potential impact

  • Unauthorized page content changes could occur
  • Malicious script content may be stored and rendered to visitors
  • Administrator or visitor sessions could be exposed through stored XSS
  • Site content, reputation, and user trust could be compromised
  • Additional administrative actions could be possible if affected endpoints expose broader mutation capabilities

General mitigation guidance

Mitigation generally focuses on restoring consistent CSRF defenses for every state-changing administrative endpoint and reducing the trust placed in browser-originated requests.

Common defensive patterns include:

  • Requiring framework-managed CSRF tokens on all administrative mutation requests
  • Avoiding unnecessary CSRF exemptions and narrowly documenting any exceptional cases
  • Applying strict server-side authorization checks independently of CSRF validation
  • Sanitizing or safely escaping stored page content according to its intended rendering context
  • Using secure cookie attributes and appropriate origin or referer validation as defense-in-depth
  • Limiting editor privileges so content authors cannot perform unrelated administrative operations

How teams detect issues like this

Organizations commonly detect this class of issue through:

  • Static analysis that identifies CSRF exemptions on state-changing views
  • Code review checks for POST, PUT, PATCH, or DELETE handlers lacking token validation
  • Tests that submit administrative mutations without valid CSRF tokens and verify rejection
  • Review of content-rendering paths for missing output encoding or sanitization
  • Policy enforcement requiring CSRF middleware and security tests for administrative routes

Automated application security and code review tools can help identify missing request-forgery protections and unsafe content-rendering patterns.

Sources

SourceLink
github.comgithub.com/batiste/django-page-cms
github.comgithub.com/batiste/django-page-cms/blob/bc4cbe6c187d2d4573289c5695ce8dec0556994d/pages/admin/views.py#L51-L53
github.comgithub.com/batiste/django-page-cms/blob/bc4cbe6c187d2d4573289c5695ce8dec0556994d/pages/placeholders.py#L238-L241
github.comgithub.com/batiste/django-page-cms/issues/244
vulncheck.comvulncheck.com/advisories/django-page-cms-through-2.0.13-csrf-via-admin-mutation-views

Frequently asked

questions

It can be triggered remotely through a malicious page, but exploitation generally depends on a signed-in editor visiting that page while an authenticated session is active.

The attacker typically does not need editor credentials. They need a way to cause an authorized editor's browser to send a request to an exposed administrative mutation endpoint.

Require valid CSRF tokens for all state-changing administrative requests, remove unjustified exemptions, and independently enforce authorization and safe output handling.

Combine framework CSRF middleware with route-level security tests, careful review of exemptions, least-privilege editor roles, and context-appropriate sanitization or output encoding for stored content.

Find out what's already
exploitable in your codebase.