Skip to content
Fencer Intel
medium 6.1

CVE-2013-6044 json

Django cross-site scripting (XSS) vulnerability via is_safe_url function

published 13y ago modified 4mo ago also GHSA-9cwg-mhxf-hh59 , PYSEC-2013-21 , EUVD-2013-0009

cvss
6.1
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 1.4.6, 1.5.2
  • python-django Debian 14, Debian 13, Debian 12 1.5.2-1

debian advisories DEBIAN-CVE-2013-6044

  • Django14 openstack 3 1.4.8-1.el6ost

red hat advisories RHSA-2013:1521

Is CVE-2013-6044 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-6044 updated cvss 4.3

python-django: xss in is_safe_url function

  • Red Hat Subscription Asset Manager Django
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 3.0 Django14 1.4.8-1.el6ost
    fixed: vendor fix RHSA-2013:1521

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.31% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi django
>=1.4, <1.4.6
>=1.5, <1.5.2
1.4.6
1.5.2

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.