Sp*tify Play Button for WordPress <= 2.10 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.11
- Affected Plugin
- Sp*tify Play Button for WordPress
- Affected Version
<= 2.10- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-41131
At a glance
CVE-2023-41131 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Sp*tify Play Button for WordPress WordPress plugin, affecting versions <= 2.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.11; sites on affected versions should update now. Disclosed October 2023, reported by BuShiYue.
Vulnerability Overview
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 settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Sp*tify Play Button for WordPress <= 2.10 carries this weakness at spotifyplaybutton_options(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Sp*tify Play Button for WordPress the fix is 2.11: builds <= 2.10 are affected, anything from 2.11 onward is not.
Remediation
Update to version 2.11, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Sp*tify Play Button for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Sp*tify Play Button for WordPress 2.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Sp*tify Play Button for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C