CVE-2011-4140

HIGHCVSS v2 · 6.87.5▲
EchelonGraph scoreLOW confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2018-07-23.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
7.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS v2: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v2.0 (legacy)
6.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 19, 2011

Last Modified

April 29, 2026

References (16)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipDjango—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-django—
  • every version up to 1.3.1-1: fixed in 1.3.1-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-django—
  • every version up to 1.3.1-1: fixed in 1.3.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-django—
  • every version up to 1.3.1-1: fixed in 1.3.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-django—
  • every version up to 1.3.1-1: fixed in 1.3.1-1
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
python-django1.0.2-1, 1.0.2-1+lenny1, 1.0.2-1+lenny2
  • every version up to 1.0.2-1+lenny3: fixed in 1.0.2-1+lenny3
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
python-django1.2.3-3, 1.2.3-3+squeeze1
  • every version up to 1.2.3-3+squeeze2: fixed in 1.2.3-3+squeeze2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django1.0.1 ... 1.3 (17 versions)
  • every version through 1.2.7: no fix on record
  • 1.3 through 1.3.1: no fix on record
  • every version up to 1.2.7: fixed in 1.2.7
  • 1.3 up to 1.3.1: fixed in 1.3.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-10-10 19:54 UTCEPSS rescore
  2. 2026-10-09 20:00 UTCEPSS rescore
  3. 2026-10-08 16:34 UTCEPSS rescore
  4. 2026-10-07 23:38 UTCEPSS rescore
  5. 2026-10-06 15:10 UTCEPSS rescore
  6. 2026-10-05 17:37 UTCEPSS rescore
  7. 2026-10-04 23:16 UTCEPSS rescore
  8. 2026-09-30 22:40 UTCOSV refresh
  9. 2026-09-30 14:58 UTCEPSS rescore
  10. 2026-09-29 08:22 UTCEG score recompute
  11. 2026-09-28 13:44 UTCEPSS rescore
  12. 2026-09-27 13:39 UTCEPSS rescore
  13. 2026-09-26 15:52 UTCEPSS rescore
  14. 2026-09-24 13:57 UTCEPSS rescore
  15. 2026-09-20 20:08 UTCEPSS rescore
  16. 2026-09-16 13:58 UTCEPSS rescore
  17. 2026-09-15 03:04 UTCEPSS rescore
  18. 2026-09-13 16:40 UTCEPSS rescore
  19. 2026-09-12 14:54 UTCEPSS rescore
  20. 2026-09-12 03:40 UTCOSV refresh
  21. 2026-09-06 13:41 UTCEPSS rescore
  22. 2026-09-05 15:22 UTCEPSS rescore
  23. 2026-09-04 13:55 UTCEPSS rescore
  24. 2026-08-25 13:43 UTCEPSS rescore
  25. 2026-08-24 09:12 UTCOSV refresh
Show 75 more
  1. 2026-08-19 16:58 UTCEPSS rescore
  2. 2026-08-18 13:42 UTCEPSS rescore
  3. 2026-08-15 01:25 UTCEPSS rescore
  4. 2026-08-09 13:41 UTCEPSS rescore
  5. 2026-08-08 16:31 UTCEPSS rescore
  6. 2026-08-08 05:49 UTCOSV refresh
  7. 2026-08-06 13:41 UTCEPSS rescore
  8. 2026-08-05 19:12 UTCEPSS rescore
  9. 2026-08-04 15:04 UTCEPSS rescore
  10. 2026-08-01 04:10 UTCEPSS rescore
  11. 2026-07-30 01:26 UTCEPSS rescore
  12. 2026-07-23 14:14 UTCEPSS rescore
  13. 2026-07-23 01:05 UTCEG score recompute
  14. 2026-07-23 00:09 UTCEG score recompute
  15. 2026-07-22 22:54 UTCOSV refresh
  16. 2026-07-22 21:48 UTCEG score recompute
  17. 2026-07-22 14:03 UTCEPSS rescore
  18. 2026-07-21 15:21 UTCEPSS rescore
  19. 2026-07-20 17:03 UTCEPSS rescore
  20. 2026-07-20 17:03 UTCEPSS rescore
  21. 2026-07-19 02:25 UTCEPSS rescore
  22. 2026-07-19 02:25 UTCEPSS rescore
  23. 2026-07-18 10:00 UTCEPSS rescore
  24. 2026-07-16 16:58 UTCEPSS rescore
  25. 2026-07-15 16:54 UTCEPSS rescore
  26. 2026-07-15 16:54 UTCEPSS rescore
  27. 2026-07-15 01:55 UTCEPSS rescore
  28. 2026-07-13 22:25 UTCEPSS rescore
  29. 2026-07-11 08:22 UTCEPSS rescore
  30. 2026-07-11 08:22 UTCEPSS rescore
  31. 2026-07-08 15:10 UTCEPSS rescore
  32. 2026-07-08 15:10 UTCEPSS rescore
  33. 2026-07-06 16:23 UTCEPSS rescore
  34. 2026-07-06 02:19 UTCEPSS rescore
  35. 2026-07-06 02:19 UTCEPSS rescore
  36. 2026-07-05 17:59 UTCOSV refresh
  37. 2026-07-05 02:26 UTCEPSS rescore
  38. 2026-07-04 06:27 UTCEPSS rescore
  39. 2026-07-02 14:01 UTCEPSS rescore
  40. 2026-07-01 15:02 UTCEPSS rescore
  41. 2026-07-01 15:02 UTCEPSS rescore
  42. 2026-06-30 23:19 UTCEPSS rescore
  43. 2026-06-30 23:19 UTCEPSS rescore
  44. 2026-06-29 14:02 UTCEPSS rescore
  45. 2026-06-28 14:03 UTCEPSS rescore
  46. 2026-06-28 04:53 UTCEPSS rescore
  47. 2026-06-28 04:52 UTCEPSS rescore
  48. 2026-06-27 03:05 UTCEPSS rescore
  49. 2026-06-27 03:05 UTCEPSS rescore
  50. 2026-06-25 13:46 UTCEPSS rescore
  51. 2026-06-24 14:02 UTCEPSS rescore
  52. 2026-06-24 14:02 UTCEPSS rescore
  53. 2026-06-23 21:30 UTCEPSS rescore
  54. 2026-06-23 21:30 UTCEPSS rescore
  55. 2026-06-22 14:22 UTCEPSS rescore
  56. 2026-06-22 14:22 UTCEPSS rescore
  57. 2026-06-21 01:56 UTCEPSS rescore
  58. 2026-06-21 01:56 UTCEPSS rescore
  59. 2026-06-19 19:22 UTCEPSS rescore
  60. 2026-06-19 19:22 UTCEPSS rescore
  61. 2026-06-18 17:49 UTCEPSS rescore
  62. 2026-06-18 17:49 UTCEPSS rescore
  63. 2026-06-17 17:49 UTCEPSS rescore
  64. 2026-06-17 17:49 UTCEPSS rescore
  65. 2026-06-17 17:49 UTCEPSS rescore
  66. 2026-06-17 05:14 UTCOSV refresh
  67. 2026-06-16 17:49 UTCEPSS rescore
  68. 2026-06-15 17:44 UTCEPSS rescore
  69. 2026-06-14 23:14 UTCEPSS rescore
  70. 2026-06-14 23:14 UTCEPSS rescore
  71. 2026-06-13 22:57 UTCEPSS rescore
  72. 2026-06-13 22:57 UTCEPSS rescore
  73. 2026-06-12 23:08 UTCEPSS rescore
  74. 2026-06-11 13:56 UTCEPSS rescore
  75. 2026-06-10 22:14 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2011-4140?
CVE-2011-4140 is a high vulnerability published on October 19, 2011. 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…
When was CVE-2011-4140 disclosed?
CVE-2011-4140 was first published on October 19, 2011, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-4140 actively exploited?
CVE-2011-4140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
How do I remediate CVE-2011-4140?
A fix for CVE-2011-4140 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2011-4140

Explore →

Is Your Infrastructure Affected by CVE-2011-4140?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs