Django CMS (5.0.x) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/django-cms-5.0.x/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 24 Aug 2026 21:57:51 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDenial of Service via Cyclic Plugin Reparenting in django CMShttps://feed.craftedsignal.io/briefs/2026-08-django-cms-dos/Mon, 24 Aug 2026 21:57:51 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-django-cms-dos/An authenticated user with plugin-change permissions can exploit the move_plugin endpoint in django CMS to create cyclic tree structures, causing resource exhaustion and denial of service during recursive SQL operations.The django CMS application is vulnerable to a denial-of-service (DoS) condition stemming from an improper validation of the move_plugin administrative endpoint (CVE-2026-54623). An authenticated user with sufficient permissions to modify plugins can purposefully move a plugin to be a child of one of its own descendants. Because the underlying recursive SQL queries used to calculate ancestors and descendants lack cycle detection or recursion depth limits, this creates an infinite loop in the database worker process. This vulnerability affects django CMS versions prior to 5.0.8. When an attacker induces this state, any subsequent request attempting to render, copy, or delete the affected plugin tree will hang, leading to application worker exhaustion and potential service outage.

Attack Chain

  1. Attacker authenticates to the django CMS dashboard with staff-level permissions.
  2. Attacker identifies a target plugin tree within a placeholder.
  3. Attacker triggers the move_plugin functionality via the administrative interface.
  4. Attacker sends a specially crafted POST request to move_plugin with the plugin_parent parameter targeting a child or descendant of the currently moved plugin.
  5. The application backend accepts the request without validating the cyclic dependency.
  6. The backend updates the database, setting the parent_id and creating a closed-loop structure in the plugin tree.
  7. Attacker triggers a legitimate action (e.g., viewing the page, editing the tree) that calls get_descendants() or get_ancestors().
  8. The database engine executes an unconstrained WITH RECURSIVE CTE, causing the application thread to hang and eventually exhausting worker capacity (DoS).

Impact

Successful exploitation results in a persistent denial-of-service condition for the affected placeholder. The application becomes unresponsive for any administrative or front-end operation involving the corrupted plugin tree. The vulnerability requires authenticated access, limiting the scope to internal users or accounts with plugin-change permissions; however, it allows for targeted service disruption within the CMS environment.

Recommendation

Prioritized actions for detection and mitigation:

  • Patch the django CMS installation to version 5.0.8 or later to incorporate the required cycle validation logic in the move_plugin endpoint.
  • Audit logs for administrative users performing high-frequency or anomalous move_plugin POST requests that might indicate attempts to manipulate the plugin tree structure.
  • Monitor application web server logs for HTTP 500 or timeout errors occurring specifically during administrative plugin operations, which may indicate the presence of cyclic tree corruption.
  • Restrict CMS_PERMISSION and plugin-change permissions to a minimal set of trusted administrative accounts to reduce the threat surface.
]]>mediumadvisory