# CVE-2026-61663: django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff > Low-privileged staff users can access placeholder structure data for non-PageContent objects without proper authorization, leading to information disclosure. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Aug 2026 - **Updated:** 25 Aug 2026 - **Also known as:** GHSA-8qj2-c6q4-f399, PYSEC-2026-3823 ## What is CVE-2026-61663? CVE-2026-61663 is a medium-severity missing authorization vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.9, render_object_structure fails to authorize non-PageContent objects that use PlaceholderRelationField. An active staff user without cms.use_structure or model-level view or change permission can request the //admin/cms/placeholder/object//structure// endpoint with guessed content_type_id and object_id values. The response discloses placeholder slot names, plugin trees, plugin identifiers, labels, and object existence for frontend-editable objects. The fix applies user_can_view_placeholder_source to the non-PageContent branch while keeping the structure board read-only for view-only users. This issue is fixed in versions 5.0.9. Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2026-61663? 3 open source packages ship an affected version, including django-cms. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `django-cms` | PyPI | All versions | 5.0.9 | | `django-cms` | PyPI | All versions | 5.0.9 | | `django-cms` | PyPI | All versions | 5.0.9 | ## How do I fix CVE-2026-61663? Upgrade django-cms to 5.0.9 or later. ## Is CVE-2026-61663 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61663 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-61663 and fix it if it is affected. What it is: CVE-2026-61663 is a medium-severity missing authorization vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61663 exists. Affected packages and fixed versions: - django-cms (PyPI): affected all versions; fixed in 5.0.9 - django-cms (PyPI): affected all versions; fixed in 5.0.9 - django-cms (PyPI): affected all versions; fixed in 5.0.9 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-61663/ (Markdown: https://insights.sbomify.com/CVE-2026-61663/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61663 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61663 - OSV: https://osv.dev/vulnerability/CVE-2026-61663 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-61663/ Summaries are generated and may contain mistakes; the official description above is the record.