Cross-Site Scripting (XSS) in djangocms-attributes-field (CVE-2024-11406)
Summary
Cross-site scripting in djangocms-attributes-field (CVE-2024-11406). Confidential information can be exposed externally. Mitigation: upgrade to 4.0.0 or later.
Original description
The description as published by the source.
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in django CMS Association django CMS Attributes Fields allows Stored XSS.
This issue affects django CMS Attributes Fields: before 4.0.
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-2024-11406 has been found in djangocms-attributes-field.
Confidential information can be exposed externally. CVSS score: 6.9/10.
What to do: upgrade djangocms-attributes-field to 4.0.0 or later.
If unsure, ask your IT team or search "djangocms-attributes-field CVE-2024-11406" on the vendor's site.
CVE-2024-11406 (djangocms-attributes-field) — CWE-79 / CVSS v3 6.9
Attack vector: remote (network-reachable)
Patched: 4.0.0 — 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.
Cross-site scripting (XSS) (CWE-79) exists in djangocms-attributes-field.
Check the vendor advisory for the affected versions of djangocms-attributes-field.
Severity: Medium (CVSS 6.9/10). Confidential information can be exposed externally.
Update to 4.0.0.
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 'djangocms-attributes-field' . 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 'djangocms-attributes-field' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
djangocms-attributes-fieldを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade djangocms-attributes-field to 4.0.0ステージング環境で 4.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package pypi.org
- package github.com
- package pypi.org
- patch github.com
- web iltosec.com
- web siberguvenlik.gov.tr
- web django-cms.org
- web usom.gov.tr
- web iltosec.com
- web django-cms.org