Skip to content

Product

wordpress w3-total-cache vulnerabilities

41 published CVES affecting wordpress w3-total-cache, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
41
Critical
5
High
20
Medium
15
Low
1
Unscored
0
CISA KEV
0

Latest wordpress w3-total-cache CVEs

Newest publication first · page 1 of 2

  1. CriticalCVSS 10.0 EPSS 2.0% Scanner template

    The W3 Total Cache WordPress plugin before 2.10.5 does not properly validate the request path it uses 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 occu...

  2. HighCVSS 7.5 EPSS 2.4% Scanner template

    The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.8.1 through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially sensitive information in the exposed log...

  3. HighCVSS 7.7 EPSS 1.9% PoC

    Guzzle, an extensible PHP HTTP client. Authorization headers on requests are sensitive information. In affected versions when using our Curl handler, it is possible to use the CURLOPT_HTTPAUTH option to specify an Authorization header. On making a request which responds with a re...

  4. MediumCVSS 6.1 EPSS 1.9% Scanner template

    The W3 Total Cache WordPress plugin before 2.1.5 was affected by a reflected Cross-Site Scripting (XSS) issue within the "extension" parameter in the Extensions dashboard, when the 'Anonymously track usage to improve product quality' setting is enabled, as the parameter is output...

  5. MediumCVSS 4.8 EPSS 0.62%

    The W3 Total Cache WordPress plugin before 2.1.3 did not sanitise or escape some of its CDN settings, allowing high privilege users to use JavaScript in them, which will be output in the page, leading to an authenticated Stored Cross-Site Scripting issue

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.