Is CVE-2026-61663 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61663 being exploited in the wild.

How severe is CVE-2026-61663?

Medium severity, with a CVSS score of 4.3, published 20 August 2026.

Which products and versions are affected?

django-cms (PyPI) < 5.0.9, ECOSYSTEM:introduced=0,fixed=5.0.9.

Is there a fix for CVE-2026-61663?

Yes. django-cms (PyPI): upgrade to 5.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-61663 attacked?

It is attacked over the network.

Am I affected by CVE-2026-61663?

Check whether you run django-cms (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61663: django CMS authorization bypass in render_object_structure

Q: Which products and versions are affected?

django-cms (PyPI) < 5.0.9, ECOSYSTEM:introduced=0,fixed=5.0.9.

Q: Is there a fix for CVE-2026-61663?

Yes. django-cms (PyPI): upgrade to 5.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-61663 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-61663?

Check whether you run django-cms (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61663 · Severity: medium · CVSS 4.3 · Published 2026-08-20

django CMS is a content management system that allows editors to manage page structure and content. A flaw in the frontend-editing structure endpoint failed to properly authorize access to non-PageContent objects, allowing any authenticated staff user to view the internal placeholder and plugin structure of objects they are not permitted to edit. This discloses editorial metadata about private objects owned by other staff members, including placeholder names, plugin hierarchy, and object existence—though not actual field data or write access.

Technologies: django-cms (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-61663 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61663 being exploited in the wild.
How severe is CVE-2026-61663?: Medium severity, with a CVSS score of 4.3, published 20 August 2026.
Which products and versions are affected?: django-cms (PyPI) < 5.0.9, ECOSYSTEM:introduced=0,fixed=5.0.9.
Is there a fix for CVE-2026-61663?: Yes. django-cms (PyPI): upgrade to 5.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61663 attacked?: It is attacked over the network.
Am I affected by CVE-2026-61663?: Check whether you run django-cms (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

django-cms (PyPI): upgrade to 5.0.9 or later
```
pip install "django-cms>=5.0.9"
```

Technical details

The `render_object_structure` view in django CMS processes requests to the endpoint `GET /<lang>/admin/cms/placeholder/object/<content_type_id>/structure/<object_id>/` to expose CMS structure metadata for frontend editing. For non-PageContent objects (those using PlaceholderRelationField), the view did not perform object-level authorization checks before returning the structure. An authenticated staff user could enumerate or guess the content_type_id and object_id to retrieve placeholder/plugin trees of any object in the system, bypassing both model-level change permissions and the `cms.use_structure` permission. PageContent objects were already protected via a separate check. The vulnerability is read-only, disclosing structure metadata (placeholder slot names, plugin tree, plugin identifiers) rather than field data or edit access. Fix available in version 5.0.9 and later, which applies object-level authorization mirroring `Placeholder.has_change_permission`, returning HTTP 404 when unauthorized.

Affected products

Django CMS Project django-cms 4.0.0 through 5.0.x, and 5.1.0a1

Identifiers

CVE-2026-61663
GHSA-8qj2-c6q4-f399
PYSEC-2026-3823

Timeline

2026-08-20: disclosed: Advisory published to GitHub Advisory Database
2026: patched: Fixed in version 5.0.9

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.