← Back
CVE-2011-0696
Cross-Site Request Forgery (CSRF) in Django (CVE-2011-0696)
Summary
vulnerability in Django (CVE-2011-0696). Data can be tampered with by attackers. Mitigation: upgrade to `1.2.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2011-0696** has been found in Django.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade Django to **1.2.5** or later.
If unsure, ask your IT team or search "Django CVE-2011-0696" on the vendor's site.
CVE-2011-0696 (Django) — CWE-352 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.2.5` — 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.
📍 Affected scope
Django — .
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **1.2.5**.
🛡️ 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' .` 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Django` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Django to 1.2.5ステージング環境で 1.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
Django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.5"}]}]
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"1.1"},{"fixed":"1.1.4"},{"introduced":"1.2"},{"fixed":"1.2.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2011-0696
- advisory https://github.com/advisories/GHSA-5j2h-h5hg-3wf8
- advisory http://secunia.com/advisories/43230
- advisory http://secunia.com/advisories/43297
- advisory http://secunia.com/advisories/43382
- advisory http://secunia.com/advisories/43426
- advisory http://www.debian.org/security/2011/dsa-2163
- advisory http://www.mandriva.com/security/advisories?name=MDVSA-2011:031
- advisory http://www.ubuntu.com/usn/USN-1066-1
- advisory http://www.vupen.com/english/advisories/2011/0372
- advisory http://www.vupen.com/english/advisories/2011/0388
- advisory http://www.vupen.com/english/advisories/2011/0429
- advisory http://www.vupen.com/english/advisories/2011/0439
- advisory http://www.vupen.com/english/advisories/2011/0441
- package https://github.com/django/django
- patch https://bugzilla.redhat.com/show_bug.cgi?id=676357
- patch http://openwall.com/lists/oss-security/2011/02/09/6
- patch http://www.djangoproject.com/weblog/2011/feb/08/security/
- web http://lists.fedoraproject.org/pipermail/package-announce/2011-February/054207.html
- web http://lists.fedoraproject.org/pipermail/package-announce/2011-February/054208.html
- web http://www.securityfocus.com/bid/46296
- web https://github.com/django/django/commit/408c5c873ce1437c7eee9544ff279ecbad7e150a
- web https://github.com/django/django/commit/818e70344e7193f6ebc73c82ed574e6ce3c91afc
- web http://www.djangoproject.com/weblog/2011/feb/08/security
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-10.yaml
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-30.yaml