Browser script execution via unescaped OAuth error
Published Nov 26, 2025 · Updated Nov 28, 2025
Cross-site scripting in Spotipy before 2.25.2 allows attackers to execute JavaScript in a user's browser through an OAuth callback. RequestHandler.do_GET in spotipy/oauth2.py places the URL-derived error parameter directly into an HTML status response without escaping it. Exploitation requires an active localhost OAuth callback server and user interaction with a crafted loopback URL; execution is limited to the localhost origin.
Summary
What happened
Cross-site scripting in Spotipy before 2.25.2 allows attackers to execute JavaScript in a user's browser through an OAuth callback. RequestHandler.do_GET in spotipy/oauth2.py places the URL-derived error parameter directly into an HTML status response without escaping it. Exploitation requires an active localhost OAuth callback server and user interaction with a crafted loopback URL; execution is limited to the localhost origin.
The record
- CVE
- CVE-2025-66040
- Published
- Nov 26, 2025
- Updated
- Nov 28, 2025
- Vendor
- Spotipy
- Product
- Spotipy
- Classifications
- CWE-79, T1204.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2025CVE publishedPublication date reported by the CVE source.
- Nov 28, 2025Record 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.
- Affected versionversion=< 2.25.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- OAuth callback reflected-XSS proof of conceptproof of concept · demonstrated
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