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