CVE-2026-75526

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. From 5.0.8 until 5.0.9, ContentRenderer.render_placeholder in cms/plugin_rendering.py can pass stored, attacker-controlled values to ContentRenderer.render_exception when plugin rendering fails in edit mode. Values from get_short_description(), the exception message, the placeholder, or placeholder.source are interpolated into a cms-rendering-exception heading and later returned through mark_safe. Because the heading is not escaped, stored HTML executes in an editor’s browser, and settings.DEBUG does not prevent the custom heading from rendering. The fix uses format_html to escape the message before safe placeholder output is returned. This issue is fixed in versions 5.0.9.

CVSS v3
4.4
EG Score
4.4(low)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 2026

Advisory Details (4)

Auto-updated Aug 20, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

5.0.9

Patch available: django-cms/django-cms 5.0.9

https://github.com/django-cms/django-cms/releases/tag/5.0.9
github_commit Patch Available

commit b56a568844ff (django-cms/django-cms)

Patch available: django-cms/django-cms 5.0.9 (contains commit b56a568844ff)

https://github.com/django-cms/django-cms/commit/b56a568844ff3702495945f73a31d0868285bf88
github_pr Patch Available

fix: Page title leaked unescaped into rendering error message, clipboard could be cleared by get request (#8699)

Patch available: django-cms/django-cms 5.0.9 (PR #8711 merged 2026-06-30)

https://github.com/django-cms/django-cms/pull/8711
github Patch Available

Stored XSS in edit-mode plugin exception rendering · Advisory · django-cms/django-cms · GitHub

https://github.com/django-cms/django-cms/security/advisories/GHSA-hvq6-2r72-p2x7

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 18:22 UTCEG score recompute
  2. 2026-08-20 18:21 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-75526?
CVE-2026-75526 is a medium vulnerability published on August 20, 2026. django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. From 5.0.8 until 5.0.9, ContentRenderer.renderplaceholder in cms/pluginrendering.py can pass stored, attacker-controlled values to ContentRenderer.renderexception when plugin rendering fails…
When was CVE-2026-75526 disclosed?
CVE-2026-75526 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-75526?
CVE-2026-75526 has a CVSS v4.0 base score of 4.4 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-75526?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75526, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75526

Explore →

Is Your Infrastructure Affected by CVE-2026-75526?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs