Login Request a demo
Unscored severity · published Jan 16, 2015
CVE-2015-0219
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash)…
–
CVSS
7%
EPSS
No
On KEV
Description
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.
Exploitation
Is it being used?
Exploit prediction (EPSS)7.0% · higher than 94% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
DJ
Django · Djangoproject
through 1.4.17; 1.6; 1.6.1; 1.6.2; 1.6.3; 1.6.4; +8 more · source: NVD
Affected product
DJ
Django
Djangoproject
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2015-0219
CVE.org
https://www.cve.org/CVERecord?id=CVE-2015-0219
advisories.mageia.org
http://advisories.mageia.org/MGASA-2015-0026.html
lists.fedoraproject.org
http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148485.html
lists.fedoraproject.org
http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148608.html
lists.fedoraproject.org
http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148696.html
lists.opensuse.org
http://lists.opensuse.org/opensuse-updates/2015-04/msg00001.html
lists.opensuse.org
http://lists.opensuse.org/opensuse-updates/2015-09/msg00035.html
More from Django
9.8
CVE-2026-4277
Privilege abuse in GenericInlineModelAdmin
9.8
CVE-2025-59681
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7
9.8
CVE-2024-53908
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17
9.8
CVE-2023-31047
In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using one form field to upload multiple files
9.8
CVE-2022-34265
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6