CVE-2026-61663: django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff
Summary The django-cms frontend-editing structure endpoint did not perform an object-level authorization check for non-PageContent objects. Any authenticated, active staff user could request the structure endpoint for a frontend-editable object (a model using PlaceholderRelationField) and read its placeholder/plugin structure, even without permission to change that object and without the cms.usestructure permission…
Published Aug 20, 2026 · Updated Sep 4, 2026
Affected packages
django-cms
- Ecosystem
- PyPI
- Affected
- < 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
The django-cms frontend-editing structure endpoint
GET /<lang>/admin/cms/placeholder/object/<content_type_id>/structure/<object_id>/did not perform an object-level authorization check for non-`PageContent` objects. Any authenticated, active staff user could request the structure endpoint for a frontend-editable object (a model using PlaceholderRelationField) and read its placeholder/plugin structure, even without permission to change that object and without the cms.use_structure permission that the toolbar UI requires before offering structure mode.
PageContent objects were already protected (a page-view check added in GHSA/PR #8644); this advisory covers the remaining non-PageContent branch of the same view.
Severity
The issue is staff-gated and read-only, disclosing CMS structure metadata (placeholder slot names, plugin tree, plugin identifiers/labels, object existence) rather than write access or arbitrary field data.
Affected versions
- django-cms
>= 4.0.0, <= 5.0.xand5.1.0a1(the vulnerable non-PageContentbranch was introduced with the frontend-editing endpoints in 4.0)
Patched versions
- django-cms TODO: 5.0.9
Preconditions
- An authenticated, active staff account (
is_staff=True). - The deployment exposes a non-
PageContentmodel with django-cms placeholders / frontend editing (e.g. viaPlaceholderRelationField). - The attacker can guess or enumerate the target
content_type_idand object id. - The attacker needs no model/object change permission and no
cms.use_structurepermission.
Impact
A low-privileged staff user can read the editorial placeholder/plugin structure of non-PageContent objects they are not authorized to edit through the toolbar. Depending on the installed plugins and templates this may reveal placeholder names, plugin layout, plugin identifiers and the existence of objects owned by other staff users or teams. This is most relevant for deployments using third-party or custom django-cms apps that expose frontend-editable objects outside the page tree.
Proof of concept
Using django-cms' own test model placeholder_relation_field_app.FancyPoll (a non-PageContent model with a PlaceholderRelationField):
target = FancyPoll.objects.create(name="private-fancy-poll")
placeholder = rescan_placeholders_for_obj(target)["content"]
attacker = self._create_user("low_staff", is_staff=True, is_superuser=False)
# attacker has neither change_fancypoll nor cms.use_structure
with self.login_user_context(attacker):
response = self.client.get(get_object_structure_url(target, language="en"))
# Before fix: HTTP 200, body contains '"placeholder_id": "<pk>"'
# After fix: HTTP 404, structure not disclosedPatch
render_object_structure now authorizes the non-PageContent branch, mirroring Placeholder.has_change_permission at the object level (honouring a custom has_placeholder_change_permission hook, otherwise falling back to the model/object change permission) and returning 404 when the user is not authorized:
else:
content_type_obj = content_type.get_object_for_this_type(pk=object_id)
if not _can_change_placeholder_object(request.user, content_type_obj):
raise Http404Workarounds
No configuration workaround. Deployments that do not register any non-PageContent frontend-editable model are not affected. Otherwise, upgrade to a patched release.
Credit
Reported by doanmanhducz.
Credited to doanmanhducz, nichoc0.
References
- https://github.com/django-cms/django-cms/security/advisories/GHSA-8qj2-c6q4-f399
- https://github.com/django-cms/django-cms/pull/8703
- https://github.com/django-cms/django-cms/commit/9c82abfeb25471583e23906ea1ebef9202527b04
- https://github.com/django-cms/django-cms/releases/tag/5.0.9
- https://github.com/advisories/GHSA-8qj2-c6q4-f399
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-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
