Vulnerabilities and security researches forw3-total-cache w3-total-cache
Direction: ascendingJun 07, 2024
W3 Total Cache # CVE-2014-8724
- CVE, Research URL
- Home page URL
- Application
- Date
- Dec 19, 2014
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2013-2010
- CVE, Research URL
- Home page URL
- Application
- Date
- Feb 12, 2020
- Research Description
- WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2019-6715
- CVE, Research URL
- Home page URL
- Application
- Date
- Apr 02, 2019
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2021-24436
- CVE, Research URL
- Home page URL
- Application
- Date
- Jul 19, 2021
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2014-9414
- CVE, Research URL
- Home page URL
- Application
- Date
- Dec 24, 2014
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2021-24452
- CVE, Research URL
- Home page URL
- Application
- Date
- Jul 19, 2021
- Research Description
- 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 compromise.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2021-24427
- CVE, Research URL
- Home page URL
- Application
- Date
- Jul 13, 2021
- Research Description
- 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
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2012-6078
- CVE, Research URL
- Home page URL
- Application
- Date
- Nov 23, 2019
- Research Description
- W3 Total Cache before 0.9.2.5 generates hash keys insecurely which allows remote attackers to predict the values of the hashes.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2022-31090
- CVE, Research URL
- Home page URL
- Application
- Date
- Jun 28, 2022
- Research Description
- 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 the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2012-6077
- CVE, Research URL
- Home page URL
- Application
- Date
- Nov 23, 2019
- Research Description
- W3 Total Cache before 0.9.2.5 allows remote attackers to retrieve password hash information due to insecure storage of database cache files.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2012-6079
- CVE, Research URL
- Home page URL
- Application
- Date
- Nov 23, 2019
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
Sep 25, 2024
W3 Total Cache # CVE-2023-5359
- CVE, Research URL
- Home page URL
- Application
- Date
- Sep 25, 2024
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
Jan 14, 2025
W3 Total Cache # CVE-2024-12365
- CVE, Research URL
- Home page URL
- Application
- Date
- Jan 14, 2025
- Research Description
- 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 application that can be used to query information from internal services, including instance metadata on cloud-based applications.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2024-12006
- CVE, Research URL
- Home page URL
- Application
- Date
- Jan 14, 2025
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
W3 Total Cache # CVE-2024-12008
- CVE, Research URL
- Home page URL
- Application
- Date
- Jan 14, 2025
- Research Description
- 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.
- Affected versions
-
Min -, max -.
- Status
-
vulnerable
Mar 12, 2025
W3 Total Cache # PSC-2025-64559
- PSC, Research URL
- Home page URL
- Application
- Date
- -
- Research Description
- 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 Certification (PSC-2025-64559) from CleanTalk, guaranteeing a secure environment for WordPress websites.
- Affected versions
-
Min -, max -.
- Status
-
SAFE & CERTIFIED