← Back
CVE-2015-5081
high
CVSS 8.8
Cross-Site Request Forgery (CSRF) in django-cms (CVE-2015-5081)
Summary
vulnerability in django-cms (CVE-2015-5081). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2015-5081** has been found in django-cms.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade django-cms to **f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1** or later.
If unsure, ask your IT team or search "django-cms CVE-2015-5081" on the vendor's site.
CVE-2015-5081 (django-cms) — CWE-352 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: `f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1` — 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
**CSRF** (CWE-352) exists in django-cms.
📍 Affected scope
django-cms — .
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1**.
🛡️ 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 f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1ステージング環境で f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
django-cms
[{"repo":"https:\/\/github.com\/divio\/django-cms","type":"GIT","events":[{"introduced":"0"},{"fixed":"f77cbc607d6e2a62e63287d37ad320109a2cc78a"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.14"},{"introduced":"3.1"},{"fixed":"3.1.1"}]}]