CVE-2026-54623: django CMS: Plugin move endpoint allows cyclic reparenting (DoS)
Summary The moveplugin admin endpoint does not prevent a plugin from being reparented under itself or one of its own descendants. Doing so creates a cycle in the plugin tree, after which the recursive descendant/ancestor SQL queries loop without terminating, stalling the request worker.
Published Aug 24, 2026
Affected packages
django-cms
- Ecosystem
- PyPI
- Affected
- < 5.0.8
- Fixed in
- 5.0.8
- Check
pip show django-cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The move_plugin admin endpoint does not prevent a plugin from being reparented under itself or one of its own descendants. Doing so creates a cycle in the plugin tree, after which the recursive descendant/ancestor SQL queries loop without terminating, stalling the request worker.
Details
move_plugin (in cms/admin/placeholderadmin.py) accepts a plugin_parent POST parameter and, for an in-placeholder move, sets the plugin's parent to the target without any cycle/ancestor check. If the target parent is a descendant of the moved plugin, the resulting parent_id graph contains a cycle.
Descendant and ancestor traversal is implemented with WITH RECURSIVE CTEs (_get_descendants_cte / _get_ancestors_cte in cms/models/pluginmodel.py) that have no cycle clause or depth limit. On a cyclic tree these recurse indefinitely (PostgreSQL/SQLite) or error at the recursion limit (MySQL). get_descendants() is invoked while building the move response and on subsequent operations on the affected subtree.
Impact
An authenticated staff user with permission to change plugins in at least one placeholder can corrupt that placeholder's plugin tree, causing requests that traverse it (rendering, copy, delete) to hang and consume application workers (denial of service). The tree is also left in a corrupted state.
Requires CMS_PERMISSION/plugin-change permission on a placeholder.
Patches
Fixed in 5.0.8: move_plugin now rejects (HTTP 400) any move that would place a plugin inside itself or one of its descendants, before any tree mutation or traversal.
Workarounds
None. Upgrade is recommended.
Credits
Reported by the security team at the University of Sydney ([@reporter]).
Credited to Zyy0530, Str1ckl4nd, 7thParkk, mauriceng98.
References
- https://github.com/django-cms/django-cms/security/advisories/GHSA-8jj7-4v57-frf5
- https://nvd.nist.gov/vuln/detail/CVE-2026-54623
- https://github.com/django-cms/django-cms/pull/8645
- https://github.com/django-cms/django-cms/commit/7642a98ab3170793c0b27b4125dd1f3d318b8a1c
- https://github.com/django-cms/django-cms/releases/tag/5.0.8
- https://github.com/advisories/GHSA-8jj7-4v57-frf5
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-54625
django CMS: Page cache ignores plugin-declared Vary headers (disclosure & poisoning)
medium4.8Aug 24, 2026CVE-2026-54622
django CMS: Clipboard copy IDOR discloses unauthorized plugin content
medium6.5Aug 20, 2026CVE-2026-54624
django CMS: Structure endpoint bypasses page-view permission
medium6.5Aug 20, 2026CVE-2026-61663
django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff
medium4.3Aug 20, 2026CVE-2026-63003
django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction bypass)
medium6.5Aug 20, 2026CVE-2026-75526
django CMS: Stored XSS in edit-mode plugin exception rendering
medium4.4Aug 20, 2026
