Sp*tify Play Button for WordPress
spotify-play-button-for-wordpress · plugin
Known security vulnerabilities for Sp*tify Play Button for WordPress. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
1 exploitable without logging in · latest Nov 26, 2024
Listed on wordpress.org · latest 2.13 · last updated Nov 18, 2024 · 3K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2023-41131unauthenticated · needs a click≤ 2.10
WordPress Sp*tify Play Button for WordPress Plugin <= 2.10 is vulnerable to Cross Site Request Forgery (CSRF)
- Medium 6.4
CVE-2024-11192contributor+≤ 2.11
Spotify Play Button for WordPress <= 2.11 - Authenticated (Contributor+) Stored Cross-Site Scripting via spotifyplaybutton Shortcode
- Medium 5.4
CVE-2023-26536contributor+≤ 2.05
WordPress Sp*tify Play Button for WordPress Plugin <= 2.05 is vulnerable to Cross Site Scripting (XSS)
- Medium 4.8
CVE-2023-1840admin≤ 2.07
Sp*tify Play Button for WordPress <= 2.07 - Authenticated (Administrator+) Stored Cross-Site Scripting
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).