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.
Original description
The description as published by the source.
Cross-site request forgery (CSRF) vulnerability in django CMS before 3.0.14, 3.1.x before 3.1.1 allows remote attackers to manipulate privileged users into performing unknown actions via unspecified vectors.
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-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.
CSRF (CWE-352) exists in django-cms.
Check the vendor advisory for the affected versions of django-cms.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1.
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 f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1ステージング環境で f77cbc607d6e2a62e63287d37ad320109a2cc78a, 3.0.14, 3.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- web openwall.com
- web django-cms.org