CVE-2026-93456 batiste CVE debrief

Who should care

Defenders responsible for django-page-cms installations, administrators of websites using django-page-cms, and security teams monitoring for CSRF and XSS attacks should be aware of this vulnerability and take necessary actions.

Why it matters

CVE-2026-93456 is a high-severity vulnerability in django-page-cms that allows CSRF attacks and stored cross-site scripting. Defenders should verify exposure, apply patches, and monitor for suspicious activity.

• Potential for attackers to modify page content through forged requests
• Risk of stored cross-site scripting attacks against signed-in editors and visitors
• Need for verification of django-page-cms installations and exposure to this vulnerability
• Priority for applying patches or mitigations to prevent exploitation

Technical summary

The django-page-cms through 2.0.13 exempts five admin mutation views from CSRF protection, 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. The vulnerability allows CSRF attacks and stored cross-site scripting. Defenders should verify exposure of django-page-cms installations to this vulnerability and apply patches or mitigations as available. The vulnerability has a high severity and a CVSS score of 8.4.

Defensive priority

Defenders should prioritize verifying exposure of django-page-cms installations to this vulnerability and apply patches or mitigations as available.

Recommended defensive actions

• Verify django-page-cms installations for exposure to CVE-2026-93456
• Apply patches or mitigations as available
• Monitor for suspicious activity related to django-page-cms admin mutation views
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and references to source code and advisories. The django-page-cms through 2.0.13 exempts five admin mutation views from CSRF protection, allowing attackers to forge requests that modify page content. Defenders should verify exposure of django-page-cms installations to this vulnerability and apply patches or mitigations as available. The vulnerability allows CSRF attacks and stored cross-site scripting. The evidence limits of this

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.