CVE-2026-61663

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

GET /<lang>/admin/cms/placeholder/object/<content_type_id>/structure/<object_id>/

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 disclosed

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-61663 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.0.9); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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 Http404

1. What is CVE-2026-61663? CVE-2026-61663 is a medium-severity missing authorization vulnerability in django-cms (pip), affecting versions < 5.0.9. It is fixed in 5.0.9. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-61663? CVE-2026-61663 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of django-cms are affected by CVE-2026-61663? django-cms (pip) versions < 5.0.9 is affected.
4. Is there a fix for CVE-2026-61663? Yes. CVE-2026-61663 is fixed in 5.0.9. Upgrade to this version or later.
5. Is CVE-2026-61663 exploitable, and should I be worried? Whether CVE-2026-61663 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-61663 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-61663? Upgrade django-cms to 5.0.9 or later.

Other vulnerabilities in django-cms