CVE-2026-54624: django CMS: Structure endpoint bypasses page-view permission
Summary The structure-board endpoint (renderobjectstructure) renders a page's plugin structure without verifying that the requesting user is allowed to view the page. The edit and preview endpoints enforce this via renderpage(), but the structure endpoint does not, allowing a low-privileged staff user to read the plugin structure of a view-restricted page.
Published Aug 20, 2026
Affected packages
django-cms
- Ecosystem
- PyPI
- Affected
- < 5.0.8
- Fixed in
- 5.0.8
- Check
pip show django-cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The structure-board endpoint (render_object_structure) renders a page's plugin structure without verifying that the requesting user is allowed to view the page. The edit and preview endpoints enforce this via render_page(), but the structure endpoint does not, allowing a low-privileged staff user to read the plugin structure of a view-restricted page.
Details
render_object_structure (in cms/views.py) loads the PageContent object and renders cms/toolbar/structure.html directly. Unlike render_object_endpoint (used by edit/preview), which renders through render_pagecontent → render_page and calls user_can_view_page(request.user, page) (returning 404 when the user may not view the page), the structure endpoint performs no page-level authorization.
The rendered structure board includes each plugin's get_short_description() (e.g. link names/URLs, text snippets), so the content of a restricted page is disclosed, not just its shape.
Impact
A staff user (any account with is_staff=True) who lacks view permission on a view-restricted page can retrieve that page's plugin structure and short descriptions by requesting the structure endpoint with the page's content-type id and object id.
This only applies when CMS_PERMISSION=True and the page has view restrictions (or CMS_PUBLIC_FOR='staff'). Sites without per-page view restrictions are not affected.
Patches
Fixed in 5.0.8: the structure endpoint now enforces user_can_view_page() for PageContent objects, matching edit/preview.
Workarounds
None other than restricting staff access. Upgrade is recommended.
Credits
Reported by the security team at the University of Sydney ([@reporter]).
Credited to Zyy0530, Str1ckl4nd, 7thParkk, mauriceng98.
References
- https://github.com/django-cms/django-cms/security/advisories/GHSA-vgxm-h9gx-h9w7
- https://github.com/django-cms/django-cms/pull/8645
- https://github.com/django-cms/django-cms/commit/7642a98ab3170793c0b27b4125dd1f3d318b8a1c
- https://github.com/django-cms/django-cms/releases/tag/5.0.8
- https://github.com/advisories/GHSA-vgxm-h9gx-h9w7
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-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, 2026CVE-2026-75526
django CMS: Stored XSS in edit-mode plugin exception rendering
medium4.4Aug 20, 2026
