SpeedyCache <= 1.1.2 - Authenticated (Subscriber+) Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 1.1.3
- Affected Plugin
- SpeedyCache – Cache, Optimization, Performance
- Affected Version
<= 1.1.2- CVSS
- 5.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2023-49746
At a glance
CVE-2023-49746 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the SpeedyCache WordPress plugin, affecting versions <= 1.1.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.3; sites on affected versions should update now. Disclosed December 2023, reported by Yuchen Ji.
Vulnerability Overview
The SpeedyCache – Cache, Optimization, Performance plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.1.2 via the speedycache_create_test_cache() function. This makes it possible for authenticated attackers, subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
SpeedyCache <= 1.1.2 carries this weakness at speedycache_create_test_cache(), and reaching it takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For SpeedyCache the fix is 1.1.3: builds <= 1.1.2 are affected, anything from 1.1.3 onward is not.
Remediation
Update to version 1.1.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SpeedyCache 1.1.3 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