CVE-2011-4140 json
Django Cross-Site Request Forgery vulnerability
published 2011-10-19 15 y ago modified 2026-06-16 4 mo ago also GHSA-h95j-h2rv-qrg4 , PYSEC-2011-5 , EUVD-2011-0010
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.
Patch / fix
- pypi django 1.2.7, 1.3.1
- python-django Debian 14, Debian 13, Debian 12 1.3.1-1
debian advisories DEBIAN-CVE-2011-4140
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-4140 updated cvss 4.3
Django: v1.3.1, v1.2.7 multiple security flaws
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django | <=1.2.7 >=1.3, <=1.3.1 <1.2.7 >=1.3, <1.3.1 |
1.2.7 1.3.1 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
bugzilla.redhat.com
/show_bug.cgi?id=737366
web, patch, report
-
openwall.com
/lists/oss-security/2011/09/11/1
mailing-list, web, patch
-
djangoproject.com
/weblog/2011/sep/10/127/
patch, article
-
openwall.com
/lists/oss-security/2011/09/13/2
mailing-list, web, patch
-
djangoproject.com
/weblog/2011/sep/09/
patch, vendor-advisory, article
-
hermes.opensuse.org
/messages/14700881
vendor-advisory, web
-
debian.org
/security/2011/dsa-2332
vendor-advisory, web, advisory
-
secunia.com
/advisories/46614
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2011-4140
advisory
-
github.com
/advisories/GHSA-h95j-h2rv-qrg4
advisory
-
github.com
/django/django
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-5.yaml
web
-
web.archive.org
/web/20140806062902/http://secunia.com/advisories/46614
web
-
djangoproject.com
/weblog/2011/sep/09
web
-
djangoproject.com
/weblog/2011/sep/10/127
web
Sources
- CVE List CVE-2011-4140
- GitHub Advisory GHSA-h95j-h2rv-qrg4
- NVD CVE-2011-4140
- OSV PYSEC-2011-5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.