Cross-Site Scripting (XSS) in django-cms (CVE-2026-75526)
Summary
cross-site scripting in django-cms (CVE-2026-75526). Risk of unauthorized operations or information disclosure. Exploitable via ``message``. Mitigation: upgrade to `5.0.9` or later.
AI summary snake-internal / snake-material-v2
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Until patched, reduce exposure by ensuring only fully trusted staff can edit plugins whose stored fields are included in `get_short_description()`, and fix or disable plugins that can be made to raise during edit-mode rendering.パッチが適用されるまでの応急処置として、Until patched, reduce exposure by ensuring only fully trusted staff can edit plugins whose stored fields are included in `get_short_description()`, and fix or disable plugins that can be made to raise during edit-mode rendering. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade django-cms to 5.0.9ステージング環境で 5.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。