Unscored severity · published Oct 4, 2013
CVE-2013-6044
The is_safe_url function in utils/http.py in Django 1.4.x before 1.4.6, 1.5.x before 1.5.2, and 1.6 before beta 2 treats a URL's scheme as safe even if it is not HTTP or HTTPS,…
–
CVSS
2.3%
EPSS
No
On KEV
Description
The is_safe_url function in utils/http.py in Django 1.4.x before 1.4.6, 1.5.x before 1.5.2, and 1.6 before beta 2 treats a URL's scheme as safe even if it is not HTTP or HTTPS, which might introduce cross-site scripting (XSS) or other vulnerabilities into Django applications that use this function, as demonstrated by "the login view in django.contrib.auth.views" and the javascript: scheme.
Exploitation
Is it being used?
Exploit prediction (EPSS)2.3% · higher than 83% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
DJ
Django · Djangoproject
1.4; 1.4.1; 1.4.2; 1.4.4; 1.4.5; 1.5; +2 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2013-6044
CVE.org
https://www.cve.org/CVERecord?id=CVE-2013-6044
lists.opensuse.org
http://lists.opensuse.org/opensuse-updates/2013-10/msg00015.html
rhn.redhat.com
http://rhn.redhat.com/errata/RHSA-2013-1521.html
seclists.org
http://seclists.org/oss-sec/2013/q3/369
seclists.org
http://seclists.org/oss-sec/2013/q3/411
Vendor Advisory
http://secunia.com/advisories/54476
www.debian.org
http://www.debian.org/security/2013/dsa-2740
More from Django
9.8
CVE-2026-4277
Privilege abuse in GenericInlineModelAdmin
9.8
CVE-2025-59681
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7
9.8
CVE-2024-53908
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17
9.8
CVE-2023-31047
In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using one form field to upload multiple files
9.8
CVE-2022-34265
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6