CVE-2026-61663: django CMS Missing Authorization Vulnerability
MODERATECVE-2026-61663 is a MODERATE (CVSS 4.3) missing authorization vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting django CMS libraries in the PyPI ecosystem. The issue involves missing authorization in `render_object_structure` discloses non-pagecontent placeholder structure to low-privileged staff. Remediation is available by upgrading affected packages to version 5.0.9.
CVE-2026-61663 at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-61663
To remediate this vulnerability, upgrade all affected django CMS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install django-cms>=5.0.9
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show django-cms
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-61663, inspect your installed packages using pip:
pip show django-cms
Analyze the terminal output to locate any version of django CMS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.9), your application is affected.
Note: The pip show django-cms command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In django CMS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-61663 Affected django CMS Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
django-cms
|
PyPI |
< 5.0.9
|
5.0.9
|
References
Frequently Asked Questions
What is CVE-2026-61663?
Which django CMS versions are affected?
What version fixes CVE-2026-61663?
Is django-cms affected?
What is the CVSS score of CVE-2026-61663?
What CWE is associated with CVE-2026-61663?
How can I check PyPI dependencies for CVE-2026-61663?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8qj2-c6q4-f399",
"modified" : "2026-08-20T18:42:50Z",
"published" : "2026-08-20T18:42:50Z",
"aliases" : [ "CVE-2026-61663" ],
"summary" : "django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff",
"details" : "## Summary\n\nThe django-cms frontend-editing structure endpoint\n\n```\nGET /<lang>/admin/cms/placeholder/object/<content_type_id>/structure/<object_id>/\n```\n\ndid 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.\n\n`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.\n\n## Severity\n\nThe 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.\n\n## Affected versions\n\n- django-cms `>= 4.0.0, <= 5.0.x` and `5.1.0a1`\n (the vulnerable non-`PageContent` branch was introduced with the frontend-editing endpoints in 4.0)\n\n## Patched versions\n\n- django-cms TODO: 5.0.9\n\n## Preconditions\n\n- An authenticated, active staff account (`is_staff=True`).\n- The deployment exposes a non-`PageContent` model with django-cms placeholders / frontend editing (e.g. via `PlaceholderRelationField`).\n- The attacker can guess or enumerate the target `content_type_id` and object id.\n- The attacker needs **no** model/object change permission and **no** `cms.use_structure` permission.\n\n## Impact\n\nA 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.\n\n## Proof of concept\n\nUsing django-cms' own test model `placeholder_relation_field_app.FancyPoll` (a non-`PageContent` model with a `PlaceholderRelationField`):\n\n```python\ntarget = FancyPoll.objects.create(name=\"private-fancy-poll\")\nplaceholder = rescan_placeholders_for_obj(target)[\"content\"]\nattacker = self._create_user(\"low_staff\", is_staff=True, is_superuser=False)\n# attacker has neither change_fancypoll nor cms.use_structure\n\nwith self.login_user_context(attacker):\n response = self.client.get(get_object_structure_url(target, language=\"en\"))\n\n# Before fix: HTTP 200, body contains '\"placeholder_id\": \"<pk>\"'\n# After fix: HTTP 404, structure not disclosed\n```\n\n## Patch\n\n`render_object_structure` now authorizes the non-`PageContent` branch, mirroring\n`Placeholder.has_change_permission` at the object level (honouring a custom\n`has_placeholder_change_permission` hook, otherwise falling back to the model/object\nchange permission) and returning `404` when the user is not authorized:\n\n```python\nelse:\n content_type_obj = content_type.get_object_for_this_type(pk=object_id)\n if not _can_change_placeholder_object(request.user, content_type_obj):\n raise Http404\n```\n\n## Workarounds\n\nNo configuration workaround. Deployments that do not register any non-`PageContent`\nfrontend-editable model are not affected. Otherwise, upgrade to a patched release.\n\n## Credit\n\nReported by **doanmanhducz**.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "django-cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.0.9"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/django-cms/django-cms/security/advisories/GHSA-8qj2-c6q4-f399"
}, {
"type" : "WEB",
"url" : "https://github.com/django-cms/django-cms/pull/8703"
}, {
"type" : "WEB",
"url" : "https://github.com/django-cms/django-cms/commit/9c82abfeb25471583e23906ea1ebef9202527b04"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/django-cms/django-cms"
}, {
"type" : "WEB",
"url" : "https://github.com/django-cms/django-cms/releases/tag/5.0.9"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-639", "CWE-862" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-20T18:42:50Z",
"nvd_published_at" : null
}
}