Unscored severity · published Oct 19, 2011
CVE-2011-4140
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…
–
CVSS
1.1%
EPSS
No
On KEV
Description
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)1.1% · higher than 65% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
DJ
Django · Djangoproject
through 1.2.6; 0.91; 0.95; 0.95.1; 0.96; 1.0; +16 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2011-4140
CVE.org
https://www.cve.org/CVERecord?id=CVE-2011-4140
Patch
http://openwall.com/lists/oss-security/2011/09/11/1
Patch
http://openwall.com/lists/oss-security/2011/09/13/2
secunia.com
http://secunia.com/advisories/46614
www.debian.org
http://www.debian.org/security/2011/dsa-2332
Patch
https://bugzilla.redhat.com/show_bug.cgi?id=737366
hermes.opensuse.org
https://hermes.opensuse.org/messages/14700881
More from Django
9.8
CVE-2026-4277
Privilege abuse in GenericInlineModelAdmin
9.8
CVE-2025-59681
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7
9.8
CVE-2024-53908
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17
9.8
CVE-2023-31047
In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using one form field to upload multiple files
9.8
CVE-2022-34265
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6