Sp*tify Play Button for WordPress [spotify-play-button-for-wordpress] < 2.12
unknown
[en] 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. This makes it possible for authenti...
- Affected:
- up to 2.12
- Fixed in:
- 2.12
- Disclosed:
- Nov 26, 2024
CVE-2024-11192 on NVD →
Spotify Play Button for WordPress <= 2.11 - Authenticated (Contributor+) Stored Cross-Site Scripting via spotifyplaybutton Shortcode
medium
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. This makes it possible for authenticated...
- CVSS:
- 6.4
- Affected:
- up to 2.11
- Fixed in:
- 2.12
- Disclosed:
- Nov 25, 2024
CVE-2024-11192 on NVD →
Sp*tify Play Button for WordPress [spotify-play-button-for-wordpress] < 2.11
unknown
[en] Cross-Site Request Forgery (CSRF) vulnerability in Jonk @ Follow me Darling Sp*tify Play Button for WordPress plugin <= 2.10 versions.
- Affected:
- up to 2.11
- Fixed in:
- 2.11
- Disclosed:
- Oct 12, 2023
CVE-2023-41131 on NVD →
Sp*tify Play Button for WordPress <= 2.10 - Cross-Site Request Forgery
medium
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 unauthenticated attackers to modify the plugin's set...
- CVSS:
- 4.3
- Affected:
- up to 2.10
- Fixed in:
- 2.11
- Disclosed:
- Oct 3, 2023
CVE-2023-41131 on NVD →
Sp*tify Play Button for WordPress [spotify-play-button-for-wordpress] < 2.08
unknown
[en] Auth. (contributor+) Cross-Site Scripting (XSS) vulnerability in Jonk @ Follow me Darling Sp*tify Play Button for WordPress plugin <= 2.05 versions.
- Affected:
- up to 2.08
- Fixed in:
- 2.08
- Disclosed:
- Apr 5, 2023
CVE-2023-26536 on NVD →
Sp*tify Play Button for WordPress <= 2.07 - Authenticated (Administrator+) Stored Cross-Site Scripting
medium
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 administrator-level permissions and above...
- CVSS:
- 4.4
- Affected:
- up to 2.07
- Fixed in:
- 2.08
- Disclosed:
- Apr 4, 2023
CVE-2023-1840 on NVD →
Sp*tify Play Button for WordPress [spotify-play-button-for-wordpress] < 2.08
unknown
[en] 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 administrator-level permissions and...
- Affected:
- up to 2.08
- Fixed in:
- 2.08
- Disclosed:
- Apr 4, 2023
CVE-2023-1840 on NVD →
Sp*tify Play Button for WordPress <= 2.05 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
medium
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 possible for authenticated attackers with con...
- CVSS:
- 6.4
- Affected:
- up to 2.05
- Fixed in:
- 2.06
- Disclosed:
- Feb 24, 2023
CVE-2023-26536 on NVD →
Sp*tify Play Button for WordPress [spotify-play-button-for-wordpress] < 2.06
unknown
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 possible for authenticated attackers with con...
- Affected:
- up to 2.06
- Fixed in:
- 2.06
- Disclosed:
- Feb 24, 2023
Protect your WordPress site
Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.
Scan your site free
← Back to the vulnerability database