# django CMS: Stored XSS in edit-mode plugin exception rendering

Advisory record · `GHSA-hvq6-2r72-p2x7`

- **Identifiers:** `GHSA-hvq6-2r72-p2x7` · `CVE-2026-75526` · `PYSEC-2026-3825`
- **State:** Confirmed
- **Severity:** CVSS 4.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 20 Aug 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Aug 2026, 18:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django-cms` (PyPI): affected `>=5.0.8, <5.0.9`; fixed in `5.0.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions 5.0.8 up to (but not including) 5.0.9 of django CMS are affected by a stored cross-site scripting flaw in the edit-mode rendering of plugin exceptions. An editor who can store HTML in data used by a plugin's short description, and whose plugin then raises an error during edit-mode rendering, can have that HTML run in another staff user's browser. Upgrade to django-cms 5.0.9 or later. Until then, limit plugin editing to fully trusted staff and fix or disable plugins that can be made to fail during edit-mode rendering.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hvq6-2r72-p2x7)

## Sources

- [GitHub Advisory Database: GHSA-hvq6-2r72-p2x7](https://github.com/advisories/GHSA-hvq6-2r72-p2x7)
- [OSV: GHSA-hvq6-2r72-p2x7](https://osv.dev/vulnerability/GHSA-hvq6-2r72-p2x7)
- <https://github.com/django-cms/django-cms/security/advisories/GHSA-hvq6-2r72-p2x7>
- <https://github.com/django-cms/django-cms/pull/8711>
- <https://github.com/django-cms/django-cms/commit/b56a568844ff3702495945f73a31d0868285bf88>
- <https://github.com/django-cms/django-cms>
- <https://github.com/django-cms/django-cms/releases/tag/5.0.9>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hvq6-2r72-p2x7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hvq6-2r72-p2x7/>. Everything for agents: <https://agentprime.io/llms.txt>.
