WordPress plugin · spotify-play-button-for-wordpress
Is Sp*tify Play Button for WordPress safe?
Safe on 2.13 or newer.
The current version, 2.13, is past every affected range on record (5 of 5 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 5
- High or critical
- 0
- Exploited
- none
- Current version
- 2.13
- Last updated
- Nov 18, 2024
- Active installs
- 3,000+
Every recorded flaw
- Nov 26, 2024Spotify Play Button for: Stored Cross-Site ScriptingCVE-2024-11192 · affects up to 2.11 · reported by WordfenceMedium 6.4
- Jun 26, 2024Spotify Play Button: Does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embedCVE-2024-5199 · affects up to 1.0 · reported by WPScanMedium 5.4
- Oct 12, 2023Cross-Site Request Forgery (CSRF) vulnerability in Jonk @ Follow me Darling Sp*tify Play Button for WordPress plugin <= 2.10 versions.CVE-2023-41131 · affects up to 2.10 · reported by PatchstackMedium 4.3
- Apr 5, 2023Auth.CVE-2023-26536 · fixed in 2.06 · reported by PatchstackMedium 6.5
- Apr 4, 2023Sp*tify Play Button for: Stored Cross-Site ScriptingCVE-2023-1840 · affects up to 2.07 · reported by WordfenceMedium 4.4
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.