← Back
CVE-2024-11319
medium
CVSS 4.8
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in django-cms.
📍 Affected scope
django-cms — .
🔥 Severity
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.1.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade django-cms to 4.1.4ステージング環境で 4.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
django-cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.4"}]}]
PyPI
django-cms
[{"type":"ECOSYSTEM","events":[{"introduced":"4.1.2"},{"fixed":"4.1.4"}]}]
References
- advisory https://www.django-cms.org/en/blog/2024/11/13/django-cms-security-update/
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-11319
- advisory https://github.com/advisories/GHSA-gv5h-5655-h4mv
- package https://github.com/django-cms/django-cms
- report https://iltosec.com/blog/post/django-cms-413-stored-xss-vulnerability-exploiting-the-page-title-field/
- web https://github.com/django-cms/django-cms/commit/241d1cbe47a68f5d271ce4d27ad5e32e2c360ec3
- web https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-24-1859
- web https://www.usom.gov.tr/bildirim/tr-24-1859
- web https://iltosec.com/blog/post/django-cms-413-stored-xss-vulnerability-exploiting-the-page-title-field
- web https://www.django-cms.org/en/blog/2024/11/13/django-cms-security-update
- web https://github.com/pypa/advisory-database/tree/main/vulns/django-cms/PYSEC-2024-124.yaml