CVE-2011-4138 Django Might Allow CSRF Requests via URL Verification

What is CVE-2011-4138?

CVE-2011-4138 is a medium-severity server-side request forgery vulnerability in Djangoproject Django, published on 19 Oct 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-20

Which versions are affected by CVE-2011-4138?

5 open source packages ship an affected version, including django and Django. It affects 1 product.

Products include Djangoproject Django.

How do I fix CVE-2011-4138?

Upgrade django to a fixed version for your release line: 1.2.7 or 1.3.1.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2011-4138 being exploited?

There is no known exploitation of CVE-2011-4138 in the wild and no public exploit code.

Other vulnerabilities in Djangoproject Django

• CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin Critical 9.8
• CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle Critical 9.8
• CVE-2024-42005 Django SQL injection vulnerability Critical 9.8
• CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files Critical 9.8
• CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection Critical 9.8

All Djangoproject Django vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as DEBIAN-CVE-2011-4138, GHSA-wxg3-mfph-qg9w, PYSEC-2011-3.