CVE-2017-7233

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 2.4%, top 18% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%CVSS: 6.1Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
82.2%
KEV
Not listed

Published

April 4, 2017

Last Modified

May 13, 2026

References (22)

Vendor Advisories for CVE-2017-7233(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-django (1.8.7-1ubuntu8.2) @ yakkety2026-05-22ubuntu
redhatyaml-cpp-0:0.5.1-7.el7sat2018-10-16redhat
redhatpython-django-0:1.8.18-1.el7ost2017-10-31redhat
redhatpython-django-0:1.6.11-7.el7ost2017-06-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
django1.10 ... 1.9.9 (38 versions)1.8.18—

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 124 total refreshes for this CVE.

  1. 2026-07-22 22:10 UTCEG score recompute
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 14:28 UTCEPSS rescore
  7. 2026-07-19 14:28 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-18 10:01 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 01:56 UTCEPSS rescore
  16. 2026-07-15 01:56 UTCEPSS rescore
  17. 2026-07-13 22:26 UTCEPSS rescore
  18. 2026-07-13 22:26 UTCEPSS rescore
  19. 2026-07-12 05:43 UTCEPSS rescore
  20. 2026-07-12 01:22 UTCOSV refresh
  21. 2026-07-11 08:24 UTCEPSS rescore
  22. 2026-07-09 19:06 UTCEPSS rescore
  23. 2026-07-08 15:11 UTCEPSS rescore
  24. 2026-07-07 13:42 UTCEPSS rescore
  25. 2026-07-06 16:24 UTCEPSS rescore
Show 75 more
  1. 2026-07-06 16:24 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-02 16:54 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:03 UTCEPSS rescore
  12. 2026-06-28 14:04 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-27 03:06 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-23 21:30 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 07:30 UTCOSV refresh
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
  26. 2026-06-21 01:57 UTCEPSS rescore
  27. 2026-06-21 01:57 UTCEPSS rescore
  28. 2026-06-19 19:23 UTCEPSS rescore
  29. 2026-06-19 19:23 UTCEPSS rescore
  30. 2026-06-18 17:50 UTCEPSS rescore
  31. 2026-06-17 17:50 UTCEPSS rescore
  32. 2026-06-16 17:50 UTCEPSS rescore
  33. 2026-06-15 17:45 UTCEPSS rescore
  34. 2026-06-14 23:14 UTCEPSS rescore
  35. 2026-06-14 23:14 UTCEPSS rescore
  36. 2026-06-13 22:58 UTCEPSS rescore
  37. 2026-06-13 22:57 UTCEPSS rescore
  38. 2026-06-12 23:09 UTCEPSS rescore
  39. 2026-06-12 23:09 UTCEPSS rescore
  40. 2026-06-11 13:57 UTCEPSS rescore
  41. 2026-06-10 22:15 UTCEPSS rescore
  42. 2026-06-10 13:19 UTCEPSS rescore
  43. 2026-06-08 14:14 UTCEPSS rescore
  44. 2026-06-08 14:14 UTCEPSS rescore
  45. 2026-06-07 15:22 UTCEPSS rescore
  46. 2026-06-07 15:22 UTCEPSS rescore
  47. 2026-06-06 13:45 UTCEPSS rescore
  48. 2026-06-06 13:45 UTCEPSS rescore
  49. 2026-06-06 06:30 UTCOSV refresh
  50. 2026-06-05 22:44 UTCEPSS rescore
  51. 2026-06-05 22:44 UTCEPSS rescore
  52. 2026-06-05 06:08 UTCEPSS rescore
  53. 2026-06-05 06:08 UTCEPSS rescore
  54. 2026-06-04 13:10 UTCEPSS rescore
  55. 2026-06-04 13:10 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-02 20:11 UTCEPSS rescore
  58. 2026-06-01 13:49 UTCEPSS rescore
  59. 2026-06-01 13:49 UTCEPSS rescore
  60. 2026-05-31 22:28 UTCEPSS rescore
  61. 2026-05-31 00:14 UTCEPSS rescore
  62. 2026-05-31 00:14 UTCEPSS rescore
  63. 2026-05-29 13:41 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-28 13:42 UTCEPSS rescore
  66. 2026-05-27 13:38 UTCEPSS rescore
  67. 2026-05-27 13:38 UTCEPSS rescore
  68. 2026-05-26 13:42 UTCEPSS rescore
  69. 2026-05-26 07:17 UTCEPSS rescore
  70. 2026-05-26 07:17 UTCEPSS rescore
  71. 2026-05-22 21:15 UTCEPSS rescore
  72. 2026-05-22 21:15 UTCEPSS rescore
  73. 2026-05-22 21:15 UTCEPSS rescore
  74. 2026-05-22 21:15 UTCEPSS rescore
  75. 2026-05-22 21:15 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-7233?
CVE-2017-7233 is a medium vulnerability published on April 4, 2017. 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.issafeurl()) considered some numeric URLs "safe" when they shouldn't be, aka an open…
When was CVE-2017-7233 disclosed?
CVE-2017-7233 was first published in the National Vulnerability Database on April 4, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-7233 actively exploited?
CVE-2017-7233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-7233?
CVE-2017-7233 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2017-7233?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-7233, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-7233

Explore →

Is Your Infrastructure Affected by CVE-2017-7233?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs