CVE-2026-16042

LWS Optimize – All-in-One Speed Booster & Cache Tools < 3.4 - Missing Authorization

2026-08-02 00:00
Omar Elshopky

Strategic Overview

Status
Patched in 3.4
Affected Version
< 3.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-16042
View all LWS Optimize – All-in-One Speed Booster & Cache Tools vulnerabilities

At a glance

CVE-2026-16042 is a medium-severity Missing Authorization vulnerability in the LWS Optimize WordPress plugin, affecting versions < 3.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.4; sites on affected versions should update now. Disclosed August 2026, reported by Omar Elshopky.

Vulnerability Overview

The LWS Optimize – All-in-One Speed Booster & Cache Tools plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to 3.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.

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-862: Missing Authorization

Reaching this weakness in LWS Optimize < 3.4 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For LWS Optimize the fix is 3.4: builds < 3.4 are affected, anything from 3.4 onward is not.

Remediation

Update to version 3.4, 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: LWS Optimize 3.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C