W3 Total Cache at a glance
- 41 publicly disclosed vulnerabilities, 24 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
- Ranked #73 by popularity on WordPress.org (900,000+ active installs).
- The latest version is 2.11.0 (released Oct 20, 2026). The most recent security fix shipped in 2.11.0.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your W3 Total Cache version
Enter the W3 Total Cache version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “W3 Total Cache”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “W3 Total Cache”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.11.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known W3 Total Cache vulnerabilities (latest 25 of 41)
W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry
Cross-site scripting (XSS) · CVE-2026-111254
Affected versions: ≤ 2.10.7
Fixed in: 2.11.0
Severity: High 7.2 · Disclosed Oct 30, 2026
W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Predictable Minify Placeholder
Cross-site scripting (XSS) · CVE-2026-120019
Affected versions: ≤ 2.10.7
Fixed in: 2.11.0
Severity: Medium 5.4 · Disclosed Oct 30, 2026
W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-114178
Affected versions: ≤ 2.10.7
Fixed in: 2.11.0
Severity: High 7.2 · Disclosed Oct 22, 2026
W3 Total Cache <= 2.10.5 - Authenticated (Author+) Path Traversal
Arbitrary file read or deletion · CVE-2026-107321
Affected versions: ≤ 2.10.5
Fixed in: 2.10.6
Severity: Medium 6.5 · Disclosed Oct 8, 2026
W3 Total Cache <= 2.10.6 - Unauthenticated Stored Cross-Site Scripting via Comment Content
Cross-site scripting (XSS) · CVE-2026-87920
Affected versions: ≤ 2.10.6
Fixed in: 2.10.7
Severity: High 7.2 · Disclosed Oct 1, 2026
W3 Total Cache <= 2.10.5 - Unauthenticated Stored Cross-Site Scripting via LazyLoad Background Mutator
Cross-site scripting (XSS) · CVE-2026-78438
Affected versions: ≤ 2.10.5
Fixed in: 2.10.6
Severity: High 7.2 · Disclosed Sep 4, 2026
W3 Total Cache < 2.10.5 - Unauthenticated Path Traversal
Arbitrary file read or deletion · CVE-2026-18051
Affected versions: < 2.10.5
Fixed in: 2.10.5
Severity: High 7.5 · Disclosed Aug 21, 2026
W3 Total Cache <= 2.10.3 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name
Cross-site scripting (XSS) · CVE-2026-18109
Affected versions: ≤ 2.10.3
Fixed in: 2.10.4
Severity: High 7.2 · Disclosed Aug 13, 2026
W3 Total Cache <= 2.10.2 - Unauthenticated Path Traversal
Arbitrary file read or deletion · CVE-2026-66695
Affected versions: ≤ 2.10.2
Fixed in: 2.10.3
Severity: Medium 5.3 · Disclosed Jul 31, 2026
W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary File Read via 'f_array[]' Parameter
Arbitrary file read or deletion · CVE-2026-9282
Affected versions: ≤ 2.9.4
Fixed in: 2.10.0
Severity: High 7.5 · Disclosed Jul 10, 2026
W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary Code Execution
Other weakness · CVE-2026-57623
Affected versions: ≤ 2.9.4
Fixed in: 2.10.0
Severity: High 8.1 · Disclosed Jun 29, 2026
W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header
Other weakness · CVE-2026-5032
Affected versions: ≤ 2.9.3
Fixed in: 2.9.4
Severity: High 7.5 · Disclosed Apr 1, 2026
W3 Total Cache <= 2.9.1 - Missing Authorization
Missing authorization · CVE-2026-39595
Affected versions: ≤ 2.9.1
Fixed in: 2.9.2
Severity: Medium 4.3 · Disclosed Mar 12, 2026
W3 Total Cache <= 2.9.1 - Unauthenticated Arbitrary Code Execution
Other weakness · CVE-2026-27384
Affected versions: ≤ 2.9.1
Fixed in: 2.9.2
Severity: Critical 9.8 · Disclosed Feb 24, 2026
W3 Total Cache <= 2.8.12 - Unauthenticated Command Injection
Other weakness · CVE-2025-9501
Affected versions: ≤ 2.8.12
Fixed in: 2.8.13
Severity: High 8.1 · Disclosed Oct 27, 2025
W3 Total Cache <= 2.8.1 - Authenticated (Subscriber+) Missing Authorization to Server-Side Request Forgery
Missing authorization · CVE-2024-12365
Affected versions: ≤ 2.8.1
Fixed in: 2.8.2
Severity: High 8.5 · Disclosed Jan 13, 2025
W3 Total Cache <= 2.8.1 Missing Authorization to Unauthenticated Plugin Deactivation and Extensions Activation/Deactivation
Missing authorization · CVE-2024-12006
Affected versions: ≤ 2.8.1
Fixed in: 2.8.2
Severity: Medium 5.3 · Disclosed Jan 13, 2025
W3 Total Cache <= 2.8.1 Information Exposure via Log Files
Information disclosure · CVE-2024-12008
Affected versions: ≤ 2.8.1
Fixed in: 2.8.2
Severity: Medium 5.3 · Disclosed Jan 13, 2025
W3 Total Cache <= 2.7.5 - Sensitive Credentials Stored in Plaintext
Other weakness · CVE-2023-5359
Affected versions: ≤ 2.7.5
Fixed in: 2.7.6
Severity: Low 3.7 · Disclosed Sep 23, 2024
Guzzle <= 6.5.7 and 7.0-7.4.4 - Information Exposure
Information disclosure · CVE-2022-31090
Affected versions: ≤ 2.2.2
Fixed in: 2.2.3
Severity: High 7.7 · Disclosed Jun 20, 2022
W3 Total Cache <= 2.1.4 - Reflected Cross-Site Scripting via extension
Cross-site scripting (XSS) · CVE-2021-24452
Affected versions: ≥ 0.5, ≤ 2.1.4
Fixed in: 2.1.5
Severity: High 7.2 · Disclosed Jun 28, 2021
W3 Total Cache <= 2.1.3 - Reflected Cross-Site Scripting via extension
Cross-site scripting (XSS) · CVE-2021-24436
Affected versions: < 2.1.4
Fixed in: 2.1.4
Severity: Medium 6.1 · Disclosed Jun 28, 2021
W3 Total Cache <= 2.1.2 Authenticated (Admin+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-24427
Affected versions: < 2.1.3
Fixed in: 2.1.3
Severity: Medium 4.8 · Disclosed Jun 16, 2021
W3 Total Cache 0.9.2.6-0.9.3 - File Read / Directory Traversal
Arbitrary file read or deletion · CVE-2019-6715
Affected versions: ≥ 0.9.2.6, ≤ 0.9.3
Fixed in: 0.9.4
Severity: High 7.5 · Disclosed Dec 22, 2020
W3 Total Cache <= 0.9.2.4 - Password Hash Extraction
Other weakness · CVE-2012-6077
Affected versions: ≤ 0.9.2.4
Fixed in: 0.9.2.5
Severity: High 7.5 · Disclosed Sep 22, 2020
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License ExpiryCross-site scripting (XSS) · CVE-2026-111254 | ≤ 2.10.7 | 2.11.0 | High 7.2 | Oct 30, 2026 |
| W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Predictable Minify PlaceholderCross-site scripting (XSS) · CVE-2026-120019 | ≤ 2.10.7 | 2.11.0 | Medium 5.4 | Oct 30, 2026 |
| W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-114178 | ≤ 2.10.7 | 2.11.0 | High 7.2 | Oct 22, 2026 |
| W3 Total Cache <= 2.10.5 - Authenticated (Author+) Path TraversalArbitrary file read or deletion · CVE-2026-107321 | ≤ 2.10.5 | 2.10.6 | Medium 6.5 | Oct 8, 2026 |
| W3 Total Cache <= 2.10.6 - Unauthenticated Stored Cross-Site Scripting via Comment ContentCross-site scripting (XSS) · CVE-2026-87920 | ≤ 2.10.6 | 2.10.7 | High 7.2 | Oct 1, 2026 |
| W3 Total Cache <= 2.10.5 - Unauthenticated Stored Cross-Site Scripting via LazyLoad Background MutatorCross-site scripting (XSS) · CVE-2026-78438 | ≤ 2.10.5 | 2.10.6 | High 7.2 | Sep 4, 2026 |
| W3 Total Cache < 2.10.5 - Unauthenticated Path TraversalArbitrary file read or deletion · CVE-2026-18051 | < 2.10.5 | 2.10.5 | High 7.5 | Aug 21, 2026 |
| W3 Total Cache <= 2.10.3 - Unauthenticated Stored Cross-Site Scripting via Comment Author NameCross-site scripting (XSS) · CVE-2026-18109 | ≤ 2.10.3 | 2.10.4 | High 7.2 | Aug 13, 2026 |
| W3 Total Cache <= 2.10.2 - Unauthenticated Path TraversalArbitrary file read or deletion · CVE-2026-66695 | ≤ 2.10.2 | 2.10.3 | Medium 5.3 | Jul 31, 2026 |
| W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary File Read via 'f_array[]' ParameterArbitrary file read or deletion · CVE-2026-9282 | ≤ 2.9.4 | 2.10.0 | High 7.5 | Jul 10, 2026 |
| W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary Code ExecutionOther weakness · CVE-2026-57623 | ≤ 2.9.4 | 2.10.0 | High 8.1 | Jun 29, 2026 |
| W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent HeaderOther weakness · CVE-2026-5032 | ≤ 2.9.3 | 2.9.4 | High 7.5 | Apr 1, 2026 |
| W3 Total Cache <= 2.9.1 - Missing AuthorizationMissing authorization · CVE-2026-39595 | ≤ 2.9.1 | 2.9.2 | Medium 4.3 | Mar 12, 2026 |
| W3 Total Cache <= 2.9.1 - Unauthenticated Arbitrary Code ExecutionOther weakness · CVE-2026-27384 | ≤ 2.9.1 | 2.9.2 | Critical 9.8 | Feb 24, 2026 |
| W3 Total Cache <= 2.8.12 - Unauthenticated Command InjectionOther weakness · CVE-2025-9501 | ≤ 2.8.12 | 2.8.13 | High 8.1 | Oct 27, 2025 |
| W3 Total Cache <= 2.8.1 - Authenticated (Subscriber+) Missing Authorization to Server-Side Request ForgeryMissing authorization · CVE-2024-12365 | ≤ 2.8.1 | 2.8.2 | High 8.5 | Jan 13, 2025 |
| W3 Total Cache <= 2.8.1 Missing Authorization to Unauthenticated Plugin Deactivation and Extensions Activation/DeactivationMissing authorization · CVE-2024-12006 | ≤ 2.8.1 | 2.8.2 | Medium 5.3 | Jan 13, 2025 |
| W3 Total Cache <= 2.8.1 Information Exposure via Log FilesInformation disclosure · CVE-2024-12008 | ≤ 2.8.1 | 2.8.2 | Medium 5.3 | Jan 13, 2025 |
| W3 Total Cache <= 2.7.5 - Sensitive Credentials Stored in PlaintextOther weakness · CVE-2023-5359 | ≤ 2.7.5 | 2.7.6 | Low 3.7 | Sep 23, 2024 |
| Guzzle <= 6.5.7 and 7.0-7.4.4 - Information ExposureInformation disclosure · CVE-2022-31090 | ≤ 2.2.2 | 2.2.3 | High 7.7 | Jun 20, 2022 |
| W3 Total Cache <= 2.1.4 - Reflected Cross-Site Scripting via extensionCross-site scripting (XSS) · CVE-2021-24452 | ≥ 0.5, ≤ 2.1.4 | 2.1.5 | High 7.2 | Jun 28, 2021 |
| W3 Total Cache <= 2.1.3 - Reflected Cross-Site Scripting via extensionCross-site scripting (XSS) · CVE-2021-24436 | < 2.1.4 | 2.1.4 | Medium 6.1 | Jun 28, 2021 |
| W3 Total Cache <= 2.1.2 Authenticated (Admin+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-24427 | < 2.1.3 | 2.1.3 | Medium 4.8 | Jun 16, 2021 |
| W3 Total Cache 0.9.2.6-0.9.3 - File Read / Directory TraversalArbitrary file read or deletion · CVE-2019-6715 | ≥ 0.9.2.6, ≤ 0.9.3 | 0.9.4 | High 7.5 | Dec 22, 2020 |
| W3 Total Cache <= 0.9.2.4 - Password Hash ExtractionOther weakness · CVE-2012-6077 | ≤ 0.9.2.4 | 0.9.2.5 | High 7.5 | Sep 22, 2020 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.
Most common weaknesses in W3 Total Cache
Cross-site scripting (XSS)
13 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Arbitrary file read or deletion
5 issues
An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.
Information disclosure
5 issues
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is W3 Total Cache safe to use?
W3 Total Cache is a well-known plugin with 900,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.11.0) and turn on automatic updates.
How do I find which version of W3 Total Cache my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.