CVE-2011-4140

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2011-10-19 10:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:34 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.1% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2011-10-19 10:55 UTC

Last modified

2026-06-16 23:34 UTC

Exploit probability

1.1% · EPSS, next 30 days

Weakness

CWE-352 · Cross-site request forgery

Record status

Modified

Affected

• Djangoproject Django ≤ 1.2.6
• Djangoproject Django 0.91
• Djangoproject Django 0.95
• Djangoproject Django 0.95.1
• Djangoproject Django 0.96
• Djangoproject Django 1.0
• Djangoproject Django 1.0.1
• Djangoproject Django 1.0.2

Attack profile CVSS 2.0 · 6.8

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

Partial

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2011-4140.md and follow it. Check whether this project is affected by CVE-2011-4140. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge