All reports
Medium

Django open redirect and possible XSS attack via user-supplied numeric redirect URLs

Affected versions

Version ranges need review.

Affected versions
>= 1.8a1, < 1.8.18
Fixed version
1.8.18
Affected versions
>=1.10 <1.10.7 || >=1.9 <1.9.13 || >=1.8 <1.8.18
Fixed version
1.10.7 · 1.8.18 · 1.9.13
Affected versions
>= 1.10a1, < 1.10.7
Fixed version
1.10.7
Affected versions
>= 1.9a1, < 1.9.13
Fixed version
1.9.13
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2017-7233

Probability of exploitation in the next 30 days: 2.40%

FIRST EPSS · 2026-11-19

Description

Django 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an "on success" URL. The security check for these redirects (namely django.utils.http.is_safe_url()) considered some numeric URLs "safe" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.

Links

Credits

  • sunSUNQ