Skip to content
Fencer Intel
high 7.5

CVE-2011-4138 json

Django Might Allow CSRF Requests via URL Verification

published 2011-10-19 15 y ago modified 2026-06-16 4 mo ago also GHSA-wxg3-mfph-qg9w , PYSEC-2011-3 , EUVD-2011-0008

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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.

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-4138

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-4138 updated cvss 4.3

Django: v1.3.1, v1.2.7 multiple security flaws

  • Red Hat All currently supported Red Hat products
    not 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

2.41% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
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

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

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.