# CVE-2026-93456: django-page-cms through 2.0.13 CSRF via admin mutation views

> Attackers can forge requests to modify page content, enabling stored XSS against all visitors via unescaped input.

- **Severity:** High 8.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-5j3h-q5f7-g2vq

## What is CVE-2026-93456?

CVE-2026-93456 is a high-severity vulnerability in batiste django-page-cms, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-93456?


## How do I fix CVE-2026-93456?

No fix has been published for CVE-2026-93456 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93456 being exploited?

There is no known exploitation of CVE-2026-93456 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93456 and fix it if it is affected.

What it is: CVE-2026-93456 is a high-severity vulnerability in batiste django-page-cms, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93456 in the wild and no public exploit code.

Affected product: batiste django-page-cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93456/ (Markdown: https://insights.sbomify.com/CVE-2026-93456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93456
- OSV: https://osv.dev/vulnerability/CVE-2026-93456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93456/
Summaries are generated and may contain mistakes; the official description above is the record.