Skip to main content
WordPress plugin recordReviewed

W3 Total Cache vulnerability history, read against what it caches

W3 Total Cache keeps copies of pages, scripts and database objects, and can hold a CDN's access keys.

Its record titles name Comment Content, LazyLoad and Log Files. Here is how to read their version fields and which Performance screens to note.

W3 Total Cache vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 41 records for W3 Total Cache. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 2.11.0

Worked out from data retrieved on .

Every affected range listed in this source for W3 Total Cache ends before version 2.11.0.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Predictable Minify Placeholder

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 2.10.7

    Patched versions: 2.11.0

    Update to at least version 2.11.0.

  2. W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 2.10.7

    Patched versions: 2.11.0

    Update to at least version 2.11.0.

  3. W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 2.10.7

    Patched versions: 2.11.0

    Update to at least version 2.11.0.

  4. W3 Total Cache <= 2.10.5 - Authenticated (Author+) Path Traversal

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • All versions up to and including 2.10.5

    Patched versions: 2.10.6

    Update to at least version 2.10.6.

  5. W3 Total Cache <= 2.10.6 - Unauthenticated Stored Cross-Site Scripting via Comment Content

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 2.10.6

    Patched versions: 2.10.7

    Update to at least version 2.10.7.

Show 36 older records
  1. W3 Total Cache <= 2.10.5 - Unauthenticated Stored Cross-Site Scripting via LazyLoad Background Mutator

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 2.10.5

    Patched versions: 2.10.6

    Update to at least version 2.10.6.

  2. W3 Total Cache < 2.10.5 - Unauthenticated Path Traversal

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions before 2.10.5

    Patched versions: 2.10.5

    Update to at least version 2.10.5.

  3. W3 Total Cache <= 2.10.3 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 2.10.3

    Patched versions: 2.10.4

    Update to at least version 2.10.4.

  4. W3 Total Cache <= 2.10.2 - Unauthenticated Path Traversal

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 2.10.2

    Patched versions: 2.10.3

    Update to at least version 2.10.3.

  5. W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary File Read via 'f_array[]' Parameter

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 2.9.4

    Patched versions: 2.10.0

    Update to at least version 2.10.0.

  6. W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary Code Execution

    Published:
    Last updated:
    Severity:
    High (CVSS 8.1)
    Affected versions
    • All versions up to and including 2.9.4

    Patched versions: 2.10.0

    Update to at least version 2.10.0.

  7. W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 2.9.3

    Patched versions: 2.9.4

    Update to at least version 2.9.4.

  8. W3 Total Cache <= 2.9.1 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 2.9.1

    Patched versions: 2.9.2

    Update to at least version 2.9.2.

  9. W3 Total Cache <= 2.9.1 - Unauthenticated Arbitrary Code Execution

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 2.9.1

    Patched versions: 2.9.2

    Update to at least version 2.9.2.

  10. W3 Total Cache <= 2.8.12 - Unauthenticated Command Injection

    Published:
    Last updated:
    Severity:
    High (CVSS 8.1)
    Affected versions
    • All versions up to and including 2.8.12

    Patched versions: 2.8.13

    Update to at least version 2.8.13.

  11. W3 Total Cache <= 2.8.1 - Authenticated (Subscriber+) Missing Authorization to Server-Side Request Forgery

    Published:
    Last updated:
    Severity:
    High (CVSS 8.5)
    Affected versions
    • All versions up to and including 2.8.1

    Patched versions: 2.8.2

    Update to at least version 2.8.2.

  12. W3 Total Cache <= 2.8.1 Missing Authorization to Unauthenticated Plugin Deactivation and Extensions Activation/Deactivation

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 2.8.1

    Patched versions: 2.8.2

    Update to at least version 2.8.2.

  13. W3 Total Cache <= 2.8.1 Information Exposure via Log Files

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 2.8.1

    Patched versions: 2.8.2

    Update to at least version 2.8.2.

  14. W3 Total Cache <= 2.7.5 - Sensitive Credentials Stored in Plaintext

    Published:
    Last updated:
    Severity:
    Low (CVSS 3.7)
    Affected versions
    • All versions up to and including 2.7.5

    Patched versions: 2.7.6

    Update to at least version 2.7.6.

  15. Guzzle <= 6.5.7 and 7.0-7.4.4 - Information Exposure

    Published:
    Last updated:
    Severity:
    High (CVSS 7.7)
    Affected versions
    • All versions up to and including 2.2.2

    Patched versions: 2.2.3

    Update to at least version 2.2.3.

  16. W3 Total Cache <= 2.1.3 - Reflected Cross-Site Scripting via extension

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions before 2.1.4

    Patched versions: 2.1.4

    Update to at least version 2.1.4.

  17. W3 Total Cache <= 2.1.4 - Reflected Cross-Site Scripting via extension

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • From version 0.5 up to and including 2.1.4

    Patched versions: 2.1.5

    Update to at least version 2.1.5.

  18. W3 Total Cache <= 2.1.2 Authenticated (Admin+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.8)
    Affected versions
    • All versions before 2.1.3

    Patched versions: 2.1.3

    Update to at least version 2.1.3.

  19. W3 Total Cache 0.9.2.6-0.9.3 - File Read / Directory Traversal

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • From version 0.9.2.6 up to and including 0.9.3

    Patched versions: 0.9.4

    Update to at least version 0.9.4.

  20. W3 Total Cache <= 0.9.2.4 - Password Hash Extraction

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 0.9.2.4

    Patched versions: 0.9.2.5

    Update to at least version 0.9.2.5.

  21. W3 Total Cache <= 0.9.2.4 - Sensitive Information Exposure

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 0.9.2.4

    Patched versions: 0.9.2.5

    Update to at least version 0.9.2.5.

  22. W3 Total Cache <= 0.9.2.4 - Insecure Cryptography to Sensitive Information Disclosure

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 0.9.2.4

    Patched versions: 0.9.2.5

    Update to at least version 0.9.2.5.

  23. W3 Total Cache <= 0.9.7.3 - Server Side Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 0.9.7.3

    Patched versions: 0.9.7.4

    Update to at least version 0.9.7.4.

  24. W3 Total Cache <= 0.9.7.3 - Improper Input Validation via openssl_verify

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 0.9.7.3

    Patched versions: 0.9.7.4

    Update to at least version 0.9.7.4.

  25. W3 Total Cache plugin <= 0.9.7.3 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 0.9.7.3

    Patched versions: 0.9.7.4

    Update to at least version 0.9.7.4.

  26. W3 Total Cache <= 0.9.4.1 - Weak validation of Amazon SNS push messages

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 0.9.4.1

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  27. W3 Total Cache <= 0.9.4 - Server-Side Request Forgery leading to Host Information Disclosure

    Published:
    Last updated:
    Severity:
    High (CVSS 8.6)
    Affected versions
    • All versions up to and including 0.9.4

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  28. W3 Total Cache <= 0.9.4.1 - Security Token Bypass via Type Juggling

    Published:
    Last updated:
    Severity:
    Low (CVSS 3.7)
    Affected versions
    • All versions up to and including 0.9.4.1

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  29. W3 Total Cache <= 0.9.4.1 - Arbitrary File Upload

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 0.9.4.1

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  30. W3 Total Cache <= 0.9.4.1 - Authenticated Arbitrary File Download

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.9)
    Affected versions
    • All versions up to and including 0.9.4.1

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  31. W3 Total Cache <= 0.9.4.1 - Arbitrary Code Execution via settings import

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 0.9.4.1

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  32. W3 Total Cache <= 0.9.4.1 - Cross-Site Scripting via request_id

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 0.9.4.1

    Patched versions: 0.9.5

    Update to at least version 0.9.5.

  33. W3 Total Cache <= 0.9.4 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 0.9.4

    Patched versions: 0.9.4.1

    Update to at least version 0.9.4.1.

  34. W3 Total Cache <= 0.9.4 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 0.9.4

    Patched versions: 0.9.4.1

    Update to at least version 0.9.4.1.

  35. W3 Total Cache <= 0.9.4 - Cross-Site Request Forgery leading to Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 0.9.4

    Patched versions: 0.9.4.1

    Update to at least version 0.9.4.1.

  36. W3 Total Cache <= 0.9.2.8 - Remote Code Execution

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 0.9.2.8

    Patched versions: 0.9.2.9

    Update to at least version 0.9.2.9.

Check W3 Total Cache on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

What W3 Total Cache stores and where input reaches it

BoldGrid publishes W3 Total Cache on WordPress.org.

The listing's Key Features describe caching of pages and posts, CSS and JavaScript, feeds, database objects, objects and fragments, with methods that include local Disk, Redis and Memcached, plus minify, lazy load and CDN management.

The vendor's page caching guide describes page caching as storing static snapshots of fully rendered pages and serving those copies for later requests, and says the plugin's "Purge Policy: Page Cache" option lets users specify the pages and feeds to purge when new posts are created, edited, or comments are posted.

The listing's FAQ has CDN credentials, such as an Amazon S3 Access key and Secret key, entered on a tab it calls "Content Delivery Network Settings". Titles in the history name Comment Content, Comment Author Name, settings import and Log Files.

Titles also carry the access wording (Subscriber+), (Author+) and (Admin+). Separately, WordPress documents its Subscriber role as holding only the read capability and its Author role as able to publish and manage its own posts and upload files.

Recurring W3 Total Cache vulnerabilities, by title

Title phrases that recur in the history include Stored Cross-Site Scripting, Path Traversal and Arbitrary Code Execution.

The access wording in titles includes Unauthenticated, Authenticated (Subscriber+), Authenticated (Author+) and Authenticated (Admin+).

  • All versions up to and including 2.10.6, patched in 2.10.7: CVE-2026-87920, whose title ends "Unauthenticated Stored Cross-Site Scripting via Comment Content".
  • All versions up to and including 2.10.5, patched in 2.10.6: CVE-2026-78438, whose title ends "Unauthenticated Stored Cross-Site Scripting via LazyLoad Background Mutator", and CVE-2026-107321, whose title ends "Authenticated (Author+) Path Traversal".
  • All versions up to and including 2.8.1, patched in 2.8.2: CVE-2024-12365, whose title ends "Authenticated (Subscriber+) Missing Authorization to Server-Side Request Forgery".

W3 Total Cache affected versions, read from the fields

Compare the installed version with each record's affected range and patched versions field, not with its title. CVE-2022-31090 is titled "Guzzle <= 6.5.7 and 7.0-7.4.4 - Information Exposure", while its fields read all versions up to and including 2.2.2, patched in 2.2.3.

One title ending can sit on more than one record: "Unauthenticated Arbitrary Code Execution" ends the title of CVE-2026-27384 (all versions up to and including 2.9.1, patched in 2.9.2) and of CVE-2026-57623 (all versions up to and including 2.9.4, patched in 2.10.0).

Some records carry no CVE id, so match those by title. One, whose title ends "Server-Side Request Forgery leading to Host Information Disclosure", covers all versions up to and including 0.9.4 and lists 0.9.5 as patched, while other records list 0.9.4.1 as patched. That record's own fields say nothing about the versions between 0.9.4 and 0.9.5, so for it the patched version, 0.9.5, is the one to reach.

The Performance screens behind each checklist item

Review only a site you are authorised to review.

The vendor's setup guide article says the cache setup guide is shown on the first visit to a page in the Performance menu after the plugin is installed and activated, and its steps test and select cache methods. If it appears, stop and ask the site owner.

Plugin version and licence

The Plugins screen includes the version number in each row's Description column: write down the W3 Total Cache row's. 1 min read

Enabled cache modules

The vendor's guides put each switch on Performance > General Settings: Enable in the Page Cache section, Enable Object Cache and an Object Cache Method dropdown in the Object Caching section, a Minify section, and Enable Lazy Loading under User Experience. 1 min read

CDN and object cache settings

The listing's FAQ puts the CDN type in the Content Delivery Network section of the General Settings tab. 1 min read

Minification

The vendor's HTML minify article puts the library choice, the default Minify engine or HTML Tidy, in the Minify section of General Settings. 1 min read

Purge permissions

The vendor's purge log article gives the example of an administrator using the Purge Page Cache button from the WordPress dashboard, and the listing adds WP-CLI support for cache purging. 1 min read

W3 Total Cache security questions a version match leaves open

For W3 Total Cache, a version comparison settles which affected ranges in the history the installed copy falls inside.

It does not settle whether anyone exploited a flaw, what the cache held while an affected version was installed, or how the site is set up: whether pages are cached for logged-in users, which account a CDN key belongs to, whether a debug option adds comments to the page source.

Nor can it see code outside the plugin, such as the mfunc tags the vendor's page fragment article has developers emit in theme templates.

A WordPress security audit captures requests an administrator makes in plugin settings screens and replays them as a subscriber. It also takes each version from the Plugins screen, because caching changes what an outside request sees.

Frequently asked questions

The changelog on W3 Total Cache's WordPress.org listing is worth reading beside the update guidance at the top of the history. It has carried a 2.10.0 entry in which every line begins "Security:", and a later entry with the line "Fix: Redis/Memcached/CDN: Restore connection handling after 2.10.0 at-rest credential encryption". Take the installed version from the Plugins screen, read the changelog for every version you will pass through, and test Redis, Memcached and CDN connections on a staging copy where one exists.

The records on this page are the ones the source data files under the slug w3-total-cache, and being filed there does not settle what applies to Pro. On how Pro installs, the listing, under the heading "W3 Total Cache Pro Features", says W3 Total Cache has premium features, the worked example in the vendor's page fragment article has the step of installing and activating W3 Total Cache and setting the Pro licence, and the vendor's billing FAQ finds the licence key under Performance > General Settings > Licensing. Compare the Plugins screen version with every affected range and note whether a key is present. CVE-2026-111254, whose title ends "Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry", covers all versions up to and including 2.10.7 and lists 2.11.0 as patched.

The vendor's page caching guide puts cached pages in a page directory inside wp-content/cache, and the vendor's article on minifying CSS and JS expects the minified JS and CSS file in wp-content/cache/minify. The listing's FAQ has an Amazon S3 Access key and Secret key entered on the "Content Delivery Network Settings" tab. A record in the history has a title about stored credentials that does not say which credentials: CVE-2023-5359, whose title ends "Sensitive Credentials Stored in Plaintext", covers all versions up to and including 2.7.5 and lists 2.7.6 as patched.

The vendor's page fragment article for version 2.10.0 and later says a tag now references a callback registered through the w3tc_dynamic_callbacks filter instead of holding PHP or a file path. It says tags from older versions that still contain raw PHP or a file path are no longer run and must be migrated, that third-party plugins or themes that shipped legacy tags must adopt the same filter, and that a site owner cannot re-enable the old in-tag-code behaviour. Search theme and plugin files for mfunc and mclude before updating across that version.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 30 of the 41 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Source records