How severe is CVE-2015-0219?

CVE-2015-0219 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2015-0219?

CVE-2015-0219 affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-0219?

Update django to 1.4.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0219 is resolved across your whole dependency graph.

How do I detect CVE-2015-0219 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-0219 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2015-0219 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-0219, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-0219?

CVE-2015-0219 has an EPSS (Exploit Prediction Scoring System) score of 7.0%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-0219?

CVE-2015-0219 is classified as CWE-17 (CWE-17). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-0219 published, and has it been updated?

CVE-2015-0219 was published on January 16, 2015 and was last updated on October 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2015-0219 — django

MEDIUMFix: django/django@41b4bc7

CVE-2015-0219 is a medium-severity (CVSS 5.3) CWE-17 vulnerability in django. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Django WSGI Header Spoofing Vulnerability

Also known asGHSA-7qfw-j7hp-v45gPYSEC-2015-4

Published

Jan 16, 2015

Updated

Oct 5, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐍django🐍django🐍django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	all versions	1.4.18`pip install --upgrade 'django==1.4.18'`
🐍PyPI	`django`	≥ 1.6&&< 1.6.10	1.6.10`pip install --upgrade 'django==1.6.10'`
🐍PyPI	`django`	≥ 1.7&&< 1.7.3	1.7.3`pip install --upgrade 'django==1.7.3'`

Affected Products

1 product · 14 configurations

Application

djangodjangoproject

≤ 1.4.17

13 versions

1.61.6.11.6.21.6.31.6.41.6.51.6.61.6.71.6.81.6.91.71.7.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows…

djangoproject.comNVDDec 2016

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 1.4.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0219 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Ubuntu

USN-2469-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-0219 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works