CVE-2015-0219

CVE-2015-0219 is a medium-severity vulnerability in Djangoproject Django with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-17.

Key facts

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.

Frequently asked questions

What is 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) character in an HTTP header, as demonstrated by an X-Auth_User header.
How severe is CVE-2015-0219?
CVE-2015-0219 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2015-0219 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 7% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-0219?
CVE-2015-0219 primarily affects Djangoproject Django. In total, 14 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-0219?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2015-0219 published?
CVE-2015-0219 was published on 2015-01-16 and last updated on 2026-06-17.

References

Affected products (14)

More vulnerabilities in Djangoproject Django

All CVEs affecting Djangoproject Django →

Other CWE-17 vulnerabilities

Browse all CWE-17 vulnerabilities →