CVE-2024-5199: The Spotify Play Button WordPress plugin through 1.0 does not validate and escape some of its shortcode attrib

Q: How do I fix CVE-2024-5199?

spotify play button: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-5199 being exploited?

CVE-2024-5199 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-5199 affect?

CVE-2024-5199 affects spotify play button. Severity is medium (CVSS 5.4). The Spotify Play Button WordPress plugin through 1.0 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role an

Q: How urgent is CVE-2024-5199?

Priority 31/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2024-5199 is a medium-severity flaw (CVSS 5.4) affecting spotify play button. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Spotify Play Button WordPress plugin through 1.0 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-06-26
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wolfiezero

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-26 06:15 UTCPublished CVE record published
2026-06-17 08:15 UTCUpdated Record last modified

wolfiezero spotify play button UPGRADE

Affected: <= 1.0

Fixed in: newer than 1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy spotify-play-button || rpm -q spotify-play-button || spotify-play-button --version

2. UPGRADE to newer than 1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spotify-play-button

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spotify-play-button

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-5199?

spotify play button: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Is CVE-2024-5199 being exploited?

CVE-2024-5199 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-5199 affect?

CVE-2024-5199 affects spotify play button. Severity is medium (CVSS 5.4). The Spotify Play Button WordPress plugin through 1.0 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role an

How urgent is CVE-2024-5199?

Priority 31/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-41131 MEDIUM 4.3 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in Jonk @ Follow me Darling Sp*tify Play Button for WordPress

References

← Back to latest CVEs