Vulnerabilities · 2013 · Djangoproject
CVE-2013-6044
Djangoproject Django vulnerability
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.
Affected products
Django. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- secunia.com/advisories/54476 · Vendor Advisory
- www.djangoproject.com/weblog/2013/aug/13/security-releases-issued · Patch
- lists.opensuse.org/opensuse-updates/2013-10/msg00015.html
- rhn.redhat.com/errata/RHSA-2013-1521.html
- seclists.org/oss-sec/2013/q3/369
- seclists.org/oss-sec/2013/q3/411
- www.debian.org/security/2013/dsa-2740
- www.securityfocus.com/bid/61777
- nvd.nist.gov/vuln/detail/CVE-2013-6044
- cve.org/CVERecord?id=CVE-2013-6044
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.