HomeWordPress vulnerabilitiesLWS Optimize
LWS Optimize vulnerabilities
LWS Optimize has 3 known vulnerabilities in this database. The most recent published record is dated 9 Aug 2026.
- Known vulnerabilities
- 3
- Active installs
- 20,000+
- Latest version
- 4.1.6
- Last updated
- 29 Sep 2026
- Most recent
- 9 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-16032 | Medium 6.1 | Before 4.1.2 | Fixed in 4.1.2 | 9 Aug 2026 |
| Broken access control CVE-2026-16042 | Medium 4.3 | Before 3.4 | Fixed in 3.4 | 2 Aug 2026 |
| Arbitrary file read CVE-2026-12089 | Medium 4.9 | Up to 3.3.19 | Fixed in a later version (latest 4.1.6) | 13 Jun 2026 |
Read the published descriptions
- CVE-2026-16032, 9 Aug 2026
- The LWS Optimize WordPress plugin before 4.1.2 does not properly escape a value submitted through an unauthenticated analytics endpoint before storing it and rendering it in an administrative dashboard, allowing unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the affected dashboard page. CVE record
- CVE-2026-16042, 2 Aug 2026
- The LWS Optimize WordPress plugin before 3.4 does not perform a capability check on its cache-clearing actions, allowing any authenticated user, including Subscribers, to flush the site's caches and force repeated cache rebuilds. CVE record
- CVE-2026-12089, 13 Jun 2026
- The LWS Optimize - All-in-One Speed Booster & Cache Tools plugin for WordPress is vulnerable to Arbitrary File Read in versions up to, and including, 3.3.19. This is due to the combine_current_css() function trusting <link rel="stylesheet" href="..."> values harvested from page HTML and converting same-site URLs to absolute filesystem paths before reading them with file_get_contents()/Minify\CSS::add(), without enforcing that the resolved path stay within ABSPATH or have a .css extension. This makes it possible for authenticated attackers, with Editor-level access and above, to read arbitrary files. CVE record
What to do if you run LWS Optimize
If you run LWS Optimize, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new LWS Optimize vulnerabilities
Free. We email you when a new vulnerability is published for LWS Optimize, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.