Skip to main content
VulnerabilityPublished Updated

CVE-2026-93456: batiste django-page-cms · Cross-Site Request Forgery (CSRF)

Affects batiste django-page-cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.4 High.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
batistedjango-page-cmsAffected
  • <=2.0.13
Fixed in–

AI-suggested

Until an official fix is available, restrict access to the affected admin mutation views and educate editors to avoid visiting untrusted pages. Monitor for updates from the django-page-cms vendor regarding patches or official mitigations.

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.

References

Community reviews

Loading reviews…