CVE-2026-75526: django CMS: Stored XSS in edit-mode plugin exception rendering
Summary When plugin rendering fails in edit mode, django CMS renders a cms-rendering-exception block so editors can see that a placeholder could not be rendered. Older code built that block's heading by interpolating the exception message, placeholder/source strings, and the failing plugin's short description directly into an HTML string, then returned the placeholder output as safe markup.
Published Aug 20, 2026
Affected packages
django-cms
- Ecosystem
- PyPI
- Affected
- >= 5.0.8, < 5.0.9
- Fixed in
- 5.0.9
- Check
pip show django-cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When plugin rendering fails in edit mode, django CMS renders a cms-rendering-exception block so editors can see that a placeholder could not be rendered. Older code built that block's heading by interpolating the exception message, placeholder/source strings, and the failing plugin's short description directly into an HTML string, then returned the placeholder output as safe markup.
If an editor could store HTML in data used by a plugin's get_short_description() (or in other values interpolated into the exception message), and that plugin later raised during edit-mode rendering, the payload was parsed as HTML in the staff user's browser. This is a stored XSS condition in the CMS editing context.
Impact
The vulnerable path is only reached when placeholder rendering catches a plugin rendering exception:
try:
placeholder_content = "".join(plugin_content)
except Exception as e:
context["exc_info"] = sys.exc_info()
placeholder_content = self.render_exception("rendering placeholder", context, placeholder, editable)render_exception() constructs a message from values that can include stored content:
value- the exception message.placeholder- the placeholder string representation.placeholder.source- the source object string representation, such as page content.instance.get_short_description()- plugin-provided summary text, often derived from plugin model fields.
In the vulnerable implementation, that message was embedded directly into an HTML heading. The final placeholder content was later returned through mark_safe, so Django template autoescaping did not protect the heading.
settings.DEBUG does not mitigate the issue: it only controls whether Django's traceback HTML is appended. The custom heading is rendered in edit mode regardless of DEBUG.
Patch
Escape the custom exception heading before returning it as safe placeholder markup. The current fixed code uses format_html, which escapes message before inserting it into the heading:
heading = format_html('<h2 class="cms-rendering-exception-title">{}</h2>', message)The traceback HTML from ExceptionReporter.get_traceback_html() should remain separate from django CMS's custom heading; Django's traceback escaping does not protect additional HTML assembled by django CMS.
Workarounds
Until patched, reduce exposure by ensuring only fully trusted staff can edit plugins whose stored fields are included in get_short_description(), and fix or disable plugins that can be made to raise during edit-mode rendering. This is only a partial mitigation because the escaping bug is in the shared exception-rendering path.
References
cms/plugin_rendering.py-ContentRenderer.render_placeholdercms/plugin_rendering.py-ContentRenderer.render_exception- Fixed code:
heading = format_html('<h2 class="cms-rendering-exception-title">{}</h2>', message) - Regression tests:
cms.tests.test_plugin_renderers.TestExceptionCatchers.test_exception_in_plugin_render_escapes_user_content_in_edit_mode,cms.tests.test_plugin_renderers.TestLegacyRendererExceptionCatcher.test_exception_in_plugin_render_escapes_user_content_in_edit_mode
Credited to meifukun.
References
- 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/releases/tag/5.0.9
- https://github.com/advisories/GHSA-hvq6-2r72-p2x7
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-54623
django CMS: Plugin move endpoint allows cyclic reparenting (DoS)
high7.1Aug 24, 2026CVE-2026-54625
django CMS: Page cache ignores plugin-declared Vary headers (disclosure & poisoning)
medium4.8Aug 24, 2026CVE-2026-54622
django CMS: Clipboard copy IDOR discloses unauthorized plugin content
medium6.5Aug 20, 2026CVE-2026-54624
django CMS: Structure endpoint bypasses page-view permission
medium6.5Aug 20, 2026CVE-2026-61663
django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff
medium4.3Aug 20, 2026CVE-2026-63003
django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction bypass)
medium6.5Aug 20, 2026
