CVE-2011-4138

Description

The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
2.406%
chance of exploitation in the next 30 days
higher than 84.4% 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. 2022-05-14GitHub advisory published (GHSA-wxg3-mfph-qg9w)3860 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-wxg3-mfph-qg9w, affected packages:

EcosystemPackageVulnerable rangePatched
PyPIdjango< 1.2.71.2.7
PyPIdjango>= 1.3, < 1.3.11.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