Vulnerability in django-cms (CVE-2026-54624)
Summary
Vulnerability in django-cms (CVE-2026-54624). Confidential information can be exposed externally. Exploitable via render_object_structure. Mitigation: upgrade to 5.0.8 or later.
Original description
The description as published by the source.
Summary
The structure-board endpoint (render_object_structure) renders a page's plugin structure without verifying that the requesting user is allowed to view the page. The edit and preview endpoints enforce this via render_page(), but the structure endpoint does not, allowing a low-privileged staff user to read the plugin structure of a view-restricted page.
Details
render_object_structure (in cms/views.py) loads the PageContent object and renders cms/toolbar/structure.html directly. Unlike render_object_endpoint (used by edit/preview), which renders through render_pagecontent → render_page and calls user_can_view_page(request.user, page) (returning 404 when the user may not view the page), the structure endpoint performs no page-level authorization.
The rendered structure board includes each plugin's get_short_description() (e.g. link names/URLs, text snippets), so the content of a restricted page is disclosed, not just its shape.
Impact
A staff user (any account with is_staff=True) who lacks view permission on a view-restricted page can retrieve that page's plugin structure and short descriptions by requesting the structure endpoint with the page's content-type id and object id.
This only applies when CMS_PERMISSION=True and the page has view restrictions (or CMS_PUBLIC_FOR='staff'). Sites without per-page view restrictions are not affected.
Patches
Fixed in 5.0.8: the structure endpoint now enforces user_can_view_page()…
Source: GitHub Security Advisories (Global) 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-54624 has been found in django-cms.
Attackers can target a specific entry point like render_object_structure over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/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-54624" on the vendor's site.
CVE-2026-54624 (django-cms) — CWE-285 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: render_object_structure / PageContent / render_object_endpoint / render_pagecontent
Patched: 5.0.8 — apply immediately
Workaround: None other than restricting staff access.
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-285) exists in django-cms. Attackers reach the vulnerable code path via render_object_structure.
Check the vendor advisory for the affected versions of django-cms. Attack surface: render_object_structure / PageContent / render_object_endpoint / render_pagecontent.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 5.0.8.
Workaround: None other than restricting staff access.
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 temporary workaround mitigate
None other than restricting staff access.パッチが適用されるまでの応急処置として、None other than restricting staff access. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade django-cms to 5.0.8ステージング環境で 5.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。