django CMS: Missing authorization in render_object_structure discloses non-PageContent placeholder structure to low-privileged staff

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-61663: 0.34% estimated exploitation activity in the next 30 days; percentile 27.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 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.x and 5.1.0a1 (the vulnerable non-PageContent branch was introduced with the…

Published by the source

20 Aug 2026, 18:42 UTC

Last modified by the source

4 Sep 2026, 19:30 UTC

Source last checked

26 Oct 2026, 13:51 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8qj2-c6q4-f399

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61663

Advisory: django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff
IDs: CVE-2026-61663, GHSA-8qj2-c6q4-f399
Record: https://patchnext.com/advisories/cve-2026-61663 (revision 1, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: django-cms 5.0.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI django-cms: affected < 5.0.9; fixed in 5.0.9

## Suggested inspection (read-only)
- `python -m pip show django-cms`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on django-cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8qj2-c6q4-f399 (GitHub-reviewed advisory GHSA-8qj2-c6q4-f399 lists affected ranges: PyPI django-cms >=0 <5.0.9)

Commands are suggestions: review each one before running it.