CVE-2023-23608

UNRATEDCVSS · not yet scoredElevated
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS v2: —Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Spotipy is a light weight Python library for the Spotify Web API. In versions prior to 2.22.1, if a malicious URI is passed to the library, the library can be tricked into performing an operation on a different API endpoint than intended. The code Spotipy uses to parse URIs and URLs allows an attacker to insert arbitrary characters into the path that is used for API requests. Because it is possible to include "..", an attacker can redirect for example a track lookup via spotifyApi.track() to an arbitrary API endpoint like playlists, but this is possible for other endpoints as well. The impact of this vulnerability depends heavily on what operations a client application performs when it handles a URI from a user and how it uses the responses it receives from the API. This issue is patched in version 2.22.1.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

January 26, 2023

Last Modified

November 21, 2024

References (2)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
spotipy0.1 ... 2.9.0 (46 versions)2.22.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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 148 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2023-23608?
CVE-2023-23608 is a publicly disclosed vulnerability published on January 26, 2023. Spotipy is a light weight Python library for the Spotify Web API. In versions prior to 2.22.1, if a malicious URI is passed to the library, the library can be tricked into performing an operation on a different API endpoint than intended. The code Spotipy uses to parse URIs and URLs allows an…
When was CVE-2023-23608 disclosed?
CVE-2023-23608 was first published in the National Vulnerability Database on January 26, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-23608 actively exploited?
CVE-2023-23608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.3% of all scored CVEs.
How do I remediate CVE-2023-23608?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-23608, 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-2023-23608

Explore →

Is Your Infrastructure Affected by CVE-2023-23608?

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

Start Free Scan →Browse All CVEs