Skip to content
Noroxi
CVE-2014-0472· NVD / CVE Program· CNA debian

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 a

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."

MediumCVSS 5.1 · v2.0—Proof of concept Fix available
Published
Apr 23, 2014
Updated
Jun 16, 2026
EPSS
5.8% · 93th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
20 / 40 · 5.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.8%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
djangoprojectdjango
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux10.04
  • canonical ubuntu linux12.04
  • canonical ubuntu linux12.10
  • canonical ubuntu linux13.10
  • canonical ubuntu linux14.04
  • djangoproject djangoup to 1.4.10 inclusive
  • djangoproject django1.4
  • djangoproject django1.4.1
  • djangoproject django1.4.2
  • djangoproject django1.4.3
  • djangoproject django1.4.4
  • djangoproject django1.4.5
  • djangoproject django1.4.6
  • djangoproject django1.4.7
  • djangoproject django1.4.8
  • djangoproject django1.4.9
  • djangoproject django1.5
  • djangoproject django1.5.1
  • djangoproject django1.5.2
  • djangoproject django1.5.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-djangobefore 1.6.3-11.6.3-1
Debian:6.0python-djangobefore 1.2.3-3+squeeze101.2.3-3+squeeze10
Debian:7python-djangobefore 1.4.5-1+deb7u71.4.5-1+deb7u7
PyPIdjangofrom 1.5 · before 1.5.61.5.6
PyPIdjangofrom 1.6 · before 1.6.31.6.3
PyPIdjangobefore 1.4.111.4.11
Red Hat:openstack:4::el6Django14before 0:1.4.11-1.el6ost0:1.4.11-1.el6ost
Red Hat:openstack:4::el6Django14-docbefore 0:1.4.11-1.el6ost0:1.4.11-1.el6ost

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan
  • CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.
    53Plan
  • CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w
    52Plan
  • CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.
    49Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:python-django1.6.3-1 · Debian:12Package registry (OSV)
PyPI:django1.4.11Package registry (OSV)
PyPI:django1.5.6Package registry (OSV)
PyPI:django1.6.3Package registry (OSV)
red hat:Django140:1.4.11-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:Django14-doc0:1.4.11-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:72020-09-23

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+2345 d
  3. TodayOct 10, 2026+4553 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
P · data can be read
Integrity
P · data or configuration can be modified
Availability
P · the service can be disrupted
Attack complexity
High
Confidentiality impact
P
Integrity impact
P
Availability impact
P

CVSS vector

AV:N/AC:H/Au:N/C:P/I:P/A:P

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records