WPUpper Share Buttons <= 3.51 - Cross-Site Request Forgery to Custom CSS Update
Strategic Overview
- Status
- Patched in 3.52
- Affected Plugin
- WPUpper Share Buttons
- Affected Version
<= 3.51- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-13883
At a glance
CVE-2024-13883 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPUpper Share Buttons WordPress plugin, affecting versions <= 3.51. 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 3.52; sites on affected versions should update now. Disclosed February 2025, reported by Noah Stead (TurtleBurg).
Vulnerability Overview
The WPUpper Share Buttons plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.51. This is due to missing or incorrect nonce validation on the 'save_custom_css_request' function. This makes it possible for unauthenticated attackers to inject custom CSS to modify a site 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)
WPUpper Share Buttons <= 3.51 carries this weakness at save_custom_css_request, 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 WPUpper Share Buttons the fix is 3.52: builds <= 3.51 are affected, anything from 3.52 onward is not.
Remediation
Update to version 3.52, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WPUpper Share Buttons: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPUpper Share Buttons 3.52 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WPUpper Share Buttons
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C