CVE-2011-4140

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.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
1.093%
chance of exploitation in the next 30 days
higher than 66% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2011-10-19Published by the CNA10:00 UTC
  2. 2018-07-23GitHub advisory published (GHSA-h95j-h2rv-qrg4)2469 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-h95j-h2rv-qrg4, affected packages:

EcosystemPackageVulnerable rangePatched
PyPIdjango<= 1.2.7
PyPIdjango>= 1.3, <= 1.3.1

Affected products

VendorProduct
djangoprojectdjango

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources