CVE-2013-6044
N/A
Published: October 4, 2013 at 05:00 PM UTC
Updated: June 16, 2026 at 11:59 PM UTC
1 product affected across 1 vendorDjango
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%
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.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (13)
Vendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-updates/2013-10/msg00015.htmlVendor Advisoryx_refsource_REDHAT
Source: [email protected]
http://rhn.redhat.com/errata/RHSA-2013-1521.htmlThird Party Advisoryx_refsource_SECUNIAVendor Advisory
Source: [email protected]
http://secunia.com/advisories/54476Vendor Advisoryx_refsource_DEBIAN
Source: [email protected]
http://www.debian.org/security/2013/dsa-2740Quick Info
StatusMODIFIED
CWE
CWE-79
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card