What this page helps you verify fast
This hub clusters tracked records for Sp*tify Play Button for WordPress so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Sp*tify Play Button for WordPress (`spotify-play-button-for-wordpress`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2024-11192, CVE-2023-41131 and CVE-2023-1840, so operators can jump from disclosure to patch validation without scanning the full feed first.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
Affected range: Versions up to 2.11. Fixed version: 2.12.
Affected range: Versions up to 2.05. Fixed version: 2.06.
Affected range: Versions up to 2.07. Fixed version: 2.08.
Affected range: Versions up to 2.10. Fixed version: 2.11.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
| Tracked CVE | Issue Type | Affected Versions | Fixed Version | CVSS |
|---|---|---|---|---|
|
CVE-2024-11192
Spotify Play Button for WordPress <= 2.11 - Authenticated (Contributor+) Stored Cros...
|
Stored Cross-Site Scripting | Versions up to 2.11 | 2.12 | CVSS 6.4 |
|
CVE-2023-26536
Sp*tify Play Button for WordPress <= 2.05 - Authenticated (Contributor+) Stored Cros...
|
Stored Cross-Site Scripting | Versions up to 2.05 | 2.06 | CVSS 6.4 |
|
CVE-2023-1840
Sp*tify Play Button for WordPress <= 2.07 - Authenticated (Administrator+) Stored Cr...
|
Stored Cross-Site Scripting | Versions up to 2.07 | 2.08 | CVSS 4.4 |
|
CVE-2023-41131
Sp*tify Play Button for WordPress <= 2.10 - Cross-Site Request Forgery
|
Cross-Site Request Forgery | Versions up to 2.10 | 2.11 | CVSS 4.3 |
Spotify Play Button for WordPress <= 2.11 - Authenticated (Contributor+) Stored Cross-Site Scripting via spotifyplaybutton Shortcode
Sp*tify Play Button for WordPress <= 2.05 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Sp*tify Play Button for WordPress <= 2.07 - Authenticated (Administrator+) Stored Cross-Site Scripting
Sp*tify Play Button for WordPress <= 2.10 - Cross-Site Request Forgery
This hub clusters tracked records for Sp*tify Play Button for WordPress so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Spotify Play Button for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's spotifyplaybutton shortcode in all versions up to, and including, 2.1...
The Sp*tify Play Button for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.10. This is due to missing or incorrect nonce valid...
The Sp*tify Play Button for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 2.07 due to insufficient input sa...
Sorted by latest disclosure date so newly published issues surface first.
The Spotify Play Button for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's spotifyplaybutton shortcode in all versions up to, and including, 2.11 due to insufficient input sanitization and output escaping on user supplied attributes....
The Sp*tify Play Button for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.10. This is due to missing or incorrect nonce validation on the spotifyplaybutton_options() function. This makes it possible for unauthentica...
The Sp*tify Play Button for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 2.07 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with a...
The Sp*tify Play Button for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in versions up to, and including, 2.05 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possi...