medium
6.1
CWE
601 79
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2017-7233: XSS

First published: Wed Mar 29 2017(Updated: )

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.

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Djangoproject Django=1.8.0
Djangoproject Django=1.8.0-a1
Djangoproject Django=1.8.0-b1
Djangoproject Django=1.8.0-b2
Djangoproject Django=1.8.0-c1
Djangoproject Django=1.8.1
Djangoproject Django=1.8.2
Djangoproject Django=1.8.3
Djangoproject Django=1.8.4
Djangoproject Django=1.8.5
Djangoproject Django=1.8.6
Djangoproject Django=1.8.7
Djangoproject Django=1.8.8
Djangoproject Django=1.8.9
Djangoproject Django=1.8.10
Djangoproject Django=1.8.11
Djangoproject Django=1.8.12
Djangoproject Django=1.8.13
Djangoproject Django=1.8.14
Djangoproject Django=1.8.15
Djangoproject Django=1.8.16
Djangoproject Django=1.8.17
Djangoproject Django=1.9
Djangoproject Django=1.9-a1
Djangoproject Django=1.9-b1
Djangoproject Django=1.9-rc1
Djangoproject Django=1.9-rc2
Djangoproject Django=1.9.1
Djangoproject Django=1.9.2
Djangoproject Django=1.9.3
Djangoproject Django=1.9.4
Djangoproject Django=1.9.5
Djangoproject Django=1.9.6
Djangoproject Django=1.9.7
Djangoproject Django=1.9.8
Djangoproject Django=1.9.9
Djangoproject Django=1.9.10
Djangoproject Django=1.9.11
Djangoproject Django=1.9.12
Djangoproject Django=1.10.0
Djangoproject Django=1.10.0-a1
Djangoproject Django=1.10.0-b1
Djangoproject Django=1.10.0-rc1
Djangoproject Django=1.10.1
Djangoproject Django=1.10.2
Djangoproject Django=1.10.3
Djangoproject Django=1.10.4
Djangoproject Django=1.10.5
Djangoproject Django=1.10.6
redhat/python-django<1.8.18
1.8.18
redhat/python-django<1.9.13
1.9.13
redhat/python-django<1.10.7
1.10.7
redhat/python-django<1.11
1.11
pip/Django>=1.8a1<1.8.18
1.8.18
pip/Django>=1.9a1<1.9.13
1.9.13
pip/Django>=1.10a1<1.10.7
1.10.7

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2017-7233?

    CVE-2017-7233 is classified as a medium severity vulnerability.

  • How do I fix CVE-2017-7233?

    To fix CVE-2017-7233, upgrade Django to version 1.10.7, 1.9.13, or 1.8.18 or later.

  • What versions of Django are affected by CVE-2017-7233?

    CVE-2017-7233 affects Django versions 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18.

  • What type of vulnerability is CVE-2017-7233?

    CVE-2017-7233 is a security vulnerability related to improper URL validation.

  • Is user input involved in the exploitation of CVE-2017-7233?

    Yes, CVE-2017-7233 relies on user input in some cases, leading to potential security risks.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203