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

CVE-2014-3730 — django

HIGHFix: django/django@6011075

CVE-2014-3730 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Django Allows Open Redirects

Also known asGHSA-vq3h-3q7v-9prwPYSEC-2014-20
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.1%probability of exploitation in next 30 days
Lower Risk-0.01%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
0.34%1.49%2.64%3.80%1.0%3.1%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

4 pkgs affected
🐍django🐍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.util.http.is_safe_url function in Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly validate URLs, which allows remote attackers to conduct open redirect attacks via a malformed URL, as demonstrated by "http:\\djangoproject.com."

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 1.4&&< 1.4.131.4.13pip install --upgrade 'django==1.4.13'
🐍PyPIdjango≥ 1.5&&< 1.5.81.5.8pip install --upgrade 'django==1.5.8'
🐍PyPIdjango≥ 1.6&&< 1.6.51.6.5pip install --upgrade 'django==1.6.5'
🐍PyPIdjango≥ 1.7a1&&< 1.7b41.7b4pip install --upgrade 'django==1.7b4'

Affected Products

4 products · 43 configurations
OS
ubuntu linuxcanonical
5 versions
10.0412.0412.1013.1014.04
OS
debian linuxdebian
2 versions
7.08.0
Application
djangodjangoproject
26 versions
1.41.4.11.4.21.4.41.4.51.4.61.4.71.4.81.4.91.4.101.4.111.4.12
OS
opensuseopensuse
2 versions
12.313.1

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.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3730 is resolved across your whole dependency graph.

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

The django.util.http.is_safe_url function in Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly validate URLs, which allows remote attackers to conduct open redirect attacks via a malformed URL, as demonstrated by "http:\\\djangoproject.com."
O3 Security · Impact-Aware SCA

Is CVE-2014-3730 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2014-3730: django Open Redirect — Fixed in 1.4.13