NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2014-0472 — django

CRITICALFix: django/django@2a5bcb6

CVE-2014-0472 is a critical-severity (CVSS 9.8) Code Injection vulnerability in django. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Code Injection in Django

Also known asGHSA-rvq6-mrpv-m6rmPYSEC-2014-1
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
5.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk
5.10%5.87%6.63%7.39%6.9%5.8%May 26Sep 26Nov 26

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

The django.core.urlresolvers.reverse function in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 allows remote attackers to import and execute arbitrary Python modules by leveraging a view that constructs URLs using user input and a "dotted Python path."

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjangoall versions1.4.11pip install --upgrade 'django==1.4.11'
🐍PyPIdjango≥ 1.5&&< 1.5.61.5.6pip install --upgrade 'django==1.5.6'
🐍PyPIdjango≥ 1.6&&< 1.6.31.6.3pip install --upgrade 'django==1.6.3'

Affected Products

2 products · 28 configurations
OS
ubuntu linuxcanonical
5 versions
10.0412.0412.1013.1014.04
Application
djangodjangoproject
≤ 1.4.10
20 versions
1.41.4.11.4.21.4.31.4.41.4.51.4.61.4.71.4.81.4.91.51.5.1
Exploits & PoCs
2

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

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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.

Red HatModerate
ProductFixed inAdvisory
OpenStack 3 for RHEL 6Django14-0:1.4.11-1.el6ostRHSA-2014:0457
OpenStack 4 for RHEL 6Django14-0:1.4.11-1.el6ostRHSA-2014:0456

Frequently Asked Questions

The django.core.urlresolvers.reverse function in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 allows remote attackers to import and execute arbitrary Python modules by leveraging a view that constructs URLs using user input and a "dotted Python path."
O3 Security · Impact-Aware SCA

Is CVE-2014-0472 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2014-0472: django — Fixed in 1.4.11