CVE-2026-87920

W3 Total Cache versions up to 2.9.1 contain a broken access control vulnerability, potentially allowing unauthorized access to resources.

The W3 Total Cache WordPress plugin before 2.10.5 does not properly validate the request path used to build cache file names, allowing unauthenticated attackers to write a file into any existing directory on the server, inside or outside the web root, overwriting whatever occupies the target name. On Apache, the same flaw overwrites the site's .htaccess files, which breaks the site and can strip hardening rules that other security measures rely on.

The W3 Total Cache plugin versions up to 2.9.4 contain a critical vulnerability allowing unauthenticated remote arbitrary code execution. The flaw stems from insufficient input validation in the caching mechanism.

The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via LazyLoad Background Mutator in all versions up to, and including, 2.10.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the "Lazy Load Images" feature with "Process background images" to be enabled, and the malicious comment to be approved by a moderator before execution is triggered.

The W3 Total Cache plugin for WordPress up to version 2.10.3 is vulnerable to Stored Cross-Site Scripting via Comment Author Name due to insufficient input sanitization and output escaping. The vulnerability is only exploitable when the Lazy Load Images feature is enabled, as the unsafe re-emission occurs exclusively within the LazyLoad mutator's img tag rewriting step.

Path Traversal vulnerability in W3 Total Cache versions up to 2.10.2 allows an unauthenticated attacker to access files outside the root directory.

The W3 Total Cache plugin for WordPress up to version 2.9.4 is vulnerable to Directory Traversal via the setupSources function. Unauthenticated attackers can read arbitrary files on the server, potentially exposing sensitive information. Exploitation requires enabling manual minify mode and providing a specific minify filename.