| CVE/PSC | Application | Date | Affected versions | Description |
|---|---|---|---|---|
| Actual on: May 10, 2026, 15:05:04 | Entries count: 20 | |||
|
vulnerable
|
Jan 14, 2025, 13:01:37 |
Min -
Max 2.8.2
|
The W3 Total Cache plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the is_w3tc_admin_page function in all versions up to, and including, 2.8.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain the plugin's nonce value and perform unauthorized actions, resulting in information disclosure, service plan limits consumption as well as making web requests to arbitrary locations originating from the web appl... | |
|
vulnerable
|
Jan 14, 2025, 13:01:37 |
Min -
Max 2.8.2
|
The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions in all versions up to, and including, 2.8.1. This makes it possible for unauthenticated attackers to deactivate the plugin as well as activate and deactivate plugin extensions. | |
|
vulnerable
|
Jan 14, 2025, 13:01:37 |
Min -
Max 2.8.2
|
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 file. For example, the log file may contain nonce values that can be used in further CSRF attacks. Note: the debug feature must be enabled for this to be a concern, and it is disabled by default. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.4.1
|
Cross-site scripting (XSS) vulnerability in the W3 Total Cache plugin before 0.9.4.1 for WordPress, when debug mode is enabled, allows remote attackers to inject arbitrary web script or HTML via the "Cache key" in the HTML-Comments, as demonstrated by the PATH_INFO to the default URI. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.2.9
|
WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.4
|
pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via the SubscribeURL field in SubscriptionConfirmation JSON data. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 2.1.4
|
The W3 Total Cache WordPress plugin before 2.1.4 was vulnerable to a reflected Cross-Site Scripting (XSS) security vulnerability within the "extension" parameter in the Extensions dashboard, which is output in an attribute without being escaped first. This could allow an attacker, who can convince an authenticated admin into clicking a link, to run malicious JavaScript within the user's web browser, which could lead to full site compromise. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.4.1
|
The W3 Total Cache plugin before 0.9.4.1 for WordPress does not properly handle empty nonces, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks and hijack the authentication of administrators for requests that change the mobile site redirect URI via the mobile_groups[*][redirect] parameter and an empty _wpnonce parameter in the w3tc_mobile page to wp-admin/admin.php. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 2.1.5
|
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 in a JavaScript context without proper escaping. This could allow an attacker, who can convince an authenticated admin into clicking a link, to run malicious JavaScript within the user's web browser, which could lead to full site c... | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 2.1.3
|
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 | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.2.5
|
W3 Total Cache before 0.9.2.5 generates hash keys insecurely which allows remote attackers to predict the values of the hashes. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 2.2.3
|
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 redirect to a URI with a different origin (change in host, scheme or port), if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to ... | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.2.5
|
W3 Total Cache before 0.9.2.5 allows remote attackers to retrieve password hash information due to insecure storage of database cache files. | |
|
vulnerable
|
Jun 07, 2024, 08:06:41 |
Min -
Max 0.9.4.1
|
W3 Total Cache before 0.9.2.5 exposes sensitive cached database information which allows remote attackers to download this information via their hash keys. | |
|
SAFE & CERTIFIED
|
Mar 12, 2025, 18:03:31 |
Min 2.9.4
Max 2.9.4
|
W3 Total Cache (W3TC) is a powerful performance optimization plugin designed to enhance website speed, SEO rankings, and user experience. It achieves this by leveraging caching mechanisms, content delivery network (CDN) integration, and advanced web performance optimization (WPO) techniques. Trusted by over a million users, W3TC significantly reduces page load times, ensuring seamless website performance. The plugin has undergone rigorous security testing and has successfully obtained the Plugin Security Ce... | |
|
vulnerable
|
Apr 13, 2026, 20:04:34 |
Min -
Max 2.9.4
|
The W3 Total Cache plugin for WordPress is vulnerable to information exposure in all versions up to, and including, 2.9.3. This is due to the plugin bypassing its entire output buffering and processing pipeline when the request's User-Agent header contains "W3 Total Cache", which causes raw mfunc/mclude dynamic fragment HTML comments — including the W3TC_DYNAMIC_SECURITY security token — to be rendered in the page source. This makes it possible for unauthenticated attackers to discover the value of the W3TC... | |
|
vulnerable
|
Apr 24, 2026, 04:04:43 |
Min -
Max 2.8.13
|
The W3 Total Cache WordPress plugin before 2.8.13 is vulnerable to command injection via the _parse_dynamic_mfunc function, allowing unauthenticated users to execute PHP commands by submitting a comment with a malicious payload to a post. | |
|
vulnerable
|
Mar 28, 2026, 20:03:13 |
Min -
Max 2.9.1
|
Improper Validation of Specified Quantity in Input vulnerability in BoldGrid W3 Total Cache w3-total-cache allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects W3 Total Cache: from n/a through <= 2.9.1. | |
|
vulnerable
|
Sep 25, 2024, 07:09:55 |
Min -
Max 2.7.6
|
The W3 Total Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.7.5 via Google OAuth API secrets stored in plaintext in the publicly visible plugin source. This can allow unauthenticated attackers to impersonate W3 Total Cache and gain access to user account information in successful conditions. This would not impact the WordPress users site in any way. | |
|
SAFE & CERTIFIED
|
Feb 23, 2026, 11:02:53 |
Min 2.9.4
Max 2.9.4
|
Caching and performance optimization plugins can dramatically improve page speed, but they also expand the security footprint because they sit between dynamic application logic and static delivery. A cache can unintentionally store and serve private content, expose sensitive headers or debug artifacts, or create integrity issues when minification and rewrite rules transform how resources are delivered. These plugins also tend to touch high-risk areas like wp-admin configuration, filesystem writes (cache dir... | |