LWSCache <= 2.8.5 - Missing Authorization to Authenticated (Subscriber+) Limited Plugin Activation via lwscache_activatePlugin Function
Strategic Overview
- Status
- Patched in 2.9
- Affected Plugin
- LWSCache
- Affected Version
<= 2.8.5- CVSS
- 4.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2025-8147
At a glance
CVE-2025-8147 is a medium-severity Improper Authorization vulnerability in the LWSCache WordPress plugin, affecting versions <= 2.8.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.9; sites on affected versions should update now. Disclosed August 2025, reported by wesley (wcraft).
Vulnerability Overview
The LWSCache plugin for WordPress is vulnerable to unauthorized modification of data due to improper authorization on the lwscache_activatePlugin() function in all versions up to, and including, 2.8.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to activate arbitrary whitelisted LWS plugins.
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-285: Improper Authorization
LWSCache <= 2.8.5 carries this weakness at lwscache_activatePlugin(), and reaching it takes an account at Subscriber level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For LWSCache the fix is 2.9: builds <= 2.8.5 are affected, anything from 2.9 onward is not.
Remediation
Update to version 2.9, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: LWSCache 2.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C