Vulnerabilities · 2017 · Djangoproject
CVE-2017-7233
Djangoproject Django vulnerability
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.
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
- www.djangoproject.com/weblog/2017/apr/04/security-releases/ · Vendor Advisory
- www.securityfocus.com/bid/97406 · Third Party Advisory
- www.debian.org/security/2017/dsa-3835
- www.securitytracker.com/id/1038177
- access.redhat.com/errata/RHSA-2017:1445
- access.redhat.com/errata/RHSA-2017:1451
- access.redhat.com/errata/RHSA-2017:1462
- access.redhat.com/errata/RHSA-2017:1470
- nvd.nist.gov/vuln/detail/CVE-2017-7233
- cve.org/CVERecord?id=CVE-2017-7233
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.