Cross-Site Scripting (XSS) in django-cms (CVE-2024-11319)
Summary
Cross-site scripting in django-cms (CVE-2024-11319). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.1.4 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 allows Cross-Site Scripting (XSS).
This issue affects django-cms: 3.11.7, 3.11.8, 4.1.2, 4.1.3.
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-11319 has been found in django-cms.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade django-cms to 4.1.4 or later.
If unsure, ask your IT team or search "django-cms CVE-2024-11319" on the vendor's site.
CVE-2024-11319 (django-cms) — CWE-79 / CVSS v3 4.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.1.4 — 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 django-cms.
Check the vendor advisory for the affected versions of django-cms.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 4.1.4.
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 4.1.4ステージング環境で 4.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 github.com
- 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
- web github.com