django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.8, the move_plugin endpoint in cms/admin/placeholderadmin.py accepts an attacker-controlled plugin_parent value without rejecting a plugin’s own identifier or a descendant identifier. A staff user with plugin-change permission under CMS_PERMISSION can create a parent_id cycle in the plugin tree. The _get_descendants_cte and _get_ancestors_cte queries in cms/models/pluginmodel.py have no cycle guard, so get_descendants() and later rendering, copy, or delete operations can recurse indefinitely or reach a database recursion limit, corrupting the tree and consuming request workers. This issue is fixed in versions 5.0.8.

A vulnerability in django CMS prior to version 5.0.8 allows a staff user with plugin-change permission to create a parent_id cycle in the plugin tree via the move_plugin endpoint in cms/admin/placeholderadmin.py. The endpoint accepts an attacker-controlled plugin_parent value without validating against the plugin's own identifier or descendant identifiers. The recursive CTE queries _get_descendants_cte and _get_ancestors_cte in cms/models/pluginmodel.py lack cycle guards, enabling indefinite recursion or database recursion limit exhaustion. Exploitation can corrupt the plugin tree and consume request workers, effectively causing a denial of service. The vulnerability requires a staff account with CMS_PERMISSION and plugin-change rights, limiting but not eliminating risk. The issue has been patched in django CMS version 5.0.8.