Vulnerability in django-cms (CVE-2026-54623)
Summary
Vulnerability in django-cms (CVE-2026-54623). Risk of unauthorized operations or information disclosure. Exploitable via move_plugin. Mitigation: upgrade to 5.0.8 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54623 has been found in django-cms.
Attackers can target a specific entry point like move_plugin over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.1/10.
What to do: upgrade django-cms to 5.0.8 or later.
If unsure, ask your IT team or search "django-cms CVE-2026-54623" on the vendor's site.
CVE-2026-54623 (django-cms) — CWE-674 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: move_plugin / plugin_parent / parent_id / _get_descendants_cte
Patched: 5.0.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-674) exists in django-cms. Attackers reach the vulnerable code path via move_plugin.
Check the vendor advisory for the affected versions of django-cms. Attack surface: move_plugin / plugin_parent / parent_id / _get_descendants_cte.
Severity: High (CVSS 7.1/10). Risk of unauthorized operations or information disclosure.
Update to 5.0.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django-cms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django-cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
django-cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade django-cms to 5.0.8ステージング環境で 5.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- patch github.com
- web github.com
- web github.com