CVE-2014-0480

Description

The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL to be generated.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
2.287%
chance of exploitation in the next 30 days
higher than 83.5% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2014-08-26Published by the CNA14:00 UTC
  2. 2022-05-14GitHub advisory published (GHSA-f7cm-ccfp-3q4r)2818 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-f7cm-ccfp-3q4r, affected packages:

PackageVulnerable versionsFixed in
PyPI djangobefore 1.4.141.4.14
PyPI djangofrom 1.5 before 1.5.91.5.9
PyPI djangofrom 1.6 before 1.6.61.6.6

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
djangoproject django1.4no fix listed1.4.1no fix listed1.4.10no fix listed1.4.11no fix listed1.4.12no fix listed(+24 more)not listednot listednot listednot listednot listed
opensuse opensuse12.3no fix listed13.1no fix listednot listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources