CVE-2026-12089
Description
LWS Optimize plugin ≤3.3.19 allows authenticated Editors+ to read arbitrary files via a path traversal in CSS combination.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
LWS Optimize plugin ≤3.3.19 allows authenticated Editors+ to read arbitrary files via a path traversal in CSS combination.
Vulnerability
The LWS Optimize – All-in-One Speed Booster & Cache Tools plugin for WordPress (versions up to and including 3.3.19) contains an arbitrary file read vulnerability in the combine_current_css() function. The function trusts ` values harvested from page HTML and converts same-site URLs to absolute filesystem paths before reading them with file_get_contents()/Minify\CSS::add(), without enforcing that the resolved path stays within ABSPATH or has a .css extension [1].[2] The affected code is in Classes/Front/LwsOptimizeCSSManager.php` [2][3].
Exploitation
An authenticated attacker with Editor-level access or above can craft a page containing a ` tag with a manipulated href attribute that points to an arbitrary file on the server (e.g., ../../wp-config.php`). When the plugin processes that page’s CSS for combination, it resolves the href to an absolute path and reads the file contents [1]. No additional privileges or user interaction beyond being able to edit/create pages is required.
Impact
Successful exploitation allows the attacker to read arbitrary files on the WordPress server, including sensitive files such as wp-config.php (containing database credentials), .htaccess, or other system files. This leads to full information disclosure and could enable further compromise of the site [1].
Mitigation
The vulnerability is fixed in version 3.4.1, released on 2026-06-08 [1]. Users should update immediately. No workaround is provided for older versions; unpatched installations should be upgraded to the latest version.
AI Insight generated on Jun 13, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2<=3.3.19+ 1 more
- (no CPE)range: <=3.3.19
- (no CPE)range: <=3.3.19
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
3News mentions
0No linked articles in our index yet.