CVE-2024-28193Public exploitNetwork attack vector

Spotify API token disclosure via full User response

Published Mar 13, 2024 · Updated Aug 13, 2024

Sensitive data exposure in Yooooomi YourSpotify before 1.8.0 allows remote authenticated users to obtain Spotify API tokens through an account endpoint. The account route in server/src/routes/index.ts returns the complete database User object to requests authorized only by a shared public token, without removing accessToken or refreshToken fields. Possession of a public token is sufficient to read the associated Spotify profile, listening, and playlist data and to pause or resume playback through the Spotify API.

CVSS severity6.5
Medium
EPSS probability0.64%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive data exposure in Yooooomi YourSpotify before 1.8.0 allows remote authenticated users to obtain Spotify API tokens through an account endpoint. The account route in server/src/routes/index.ts returns the complete database User object to requests authorized only by a shared public token, without removing accessToken or refreshToken fields. Possession of a public token is sufficient to read the associated Spotify profile, listening, and playlist data and to pause or resume playback through the Spotify API.

The record

CVE
CVE-2024-28193
Published
Mar 13, 2024
Updated
Aug 13, 2024
Vendor
Yooooomi
Product
YourSpotify
Classifications
CWE-200, T1528
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 13, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 13, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.8.0
  2. Affected versionversion=< 1.8.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Yooooomi · YourSpotifyversion=0 <1.8.0; version=< 1.8.0

Published CVSS scores

6.5GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1528Steal Application Access Token

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo