Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site with W3 Total Cache ≤2.9.4
-
DeliverySend crafted request with malformed quantity input
-
ExploitBypass improper input validation (CWE-1284)
-
ExecutionMeet required high-complexity condition
-
PersistExecute arbitrary code on server
-
ImpactFull site compromise across scope
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Input size validation
|
| Exploitation Conditions | Exploitation targets the W3 Total Cache plugin (versions <= 2.9.4) and requires no authentication (PR:N) and no user interaction (UI:N) over the network (AV:N), so any internet-reachable WordPress site with the vulnerable plugin active is exposed. The key limiting factor is the high attack complexity (AC:H): the attacker must satisfy a specific, hard-to-control condition tied to the improper input-quantity validation (CWE-1284) - such as precise input state or timing - rather than a single trivially repeatable request, which constrains reliable exploitation. Exploitation is further gated on the plugin being installed and active at version 2.9.4 or below; the exact code path and any feature/configuration requirement are not detailed in the available data and should be confirmed via the Patchstack advisory. |
| Impact | The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H yields a base score of 9.0 (Critical): network-reachable, no privileges, no user interaction, full confidentiality/integrity/availability impact, and a changed scope. The mitigating signal is AC:H - successful exploitation requires the attacker to win a specific, non-trivial condition (e.g., a race, precise timing, or a particular input state), which lowers the practical reliability of exploitation compared with an AC:L RCE. No EPSS score, no CISA KEV entry, and no POC were provided, so there is currently no evidence of active exploitation and no public exploit identified at time of analysis; the risk is driven by the plugin's very large install base rather than by confirmed in-the-wild activity. Net assessment: a genuine high priority given unauthenticated network RCE in ubiquitous software, but the attack-complexity qualifier means it may favor determined/targeted attackers over trivial mass exploitation until (and unless) a reliable exploit emerges. Data gap: no exact affected-version floor, patched version, or advisory detail beyond the Patchstack reference is available, so remediation specifics must be confirmed with the vendor. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends specially crafted requests to a WordPress site running W3 Total Cache 2.9.4 or earlier, supplying malformed quantity/size input that the plugin fails to validate, and triggers the specific condition needed to coerce the plugin into executing attacker-controlled code - giving full control of the site. No POC has been published, and the AC:H rating means the attacker must reliably hit the required precondition, so an automated exploit would likely need tuning against the target environment. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 02, 2026
Unauthenticated arbitrary code execution affects the W3 Total Cache WordPress caching plugin in all versions up to and including 2.9.4, allowing remote attackers to execute code and fully compromise the underlying site without credentials or user interaction. The scope-changing CVSS 9.0 (Critical) rating reflects the plugin's deep hooks into WordPress request handling. There is no public exploit identified at time of analysis and no CISA KEV listing, though the high exploitability of a widely deployed plugin makes it a strong patching priority.
RemediationAI
No vendor-released patch version was identified in the provided data; upgrade to the first W3 Total Cache release above 2.9.4 as published by the vendor once confirmed, and consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/w3-total-cache/vulnerability/wordpress-w3-total-cache-plugin-2-9-4-arbitrary-code-execution-vulnerability?_s_id=cve) for the exact fixed version before deploying. Until a confirmed patched version is available, the most effective compensating control is to deactivate and remove the W3 Total Cache plugin, which stops the vulnerable code path entirely at the cost of losing caching performance; where the plugin cannot be removed, place the WordPress site behind a WAF with virtual-patching rules for this vulnerability and restrict/monitor requests to the plugin's endpoints, accepting that WAF signatures may lag and can be bypassed. Because exploitation is unauthenticated and network-facing, also rotate secrets and review the site for signs of compromise if the plugin has been internet-exposed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
W3 Total Cache (vendor CPE cpe:2.3:a:boldgrid:w3_total_cache) is one of the most widely installed WordPress performance plugins, providing page, object, database, browser, and CDN caching by intercepting and rewriting request/response handling at the application layer. The root cause is classed as CWE-1284 (Improper Validation of Specified Quantity in Input), meaning a size, count, or index value supplied in input is not properly validated before use; when combined with the plugin's code-generation and caching internals this improper input validation escalates to arbitrary code execution. Because caching plugins operate early in and across the WordPress request lifecycle, a flaw here can affect the whole site rather than a single component, consistent with the CVSS scope-changed (S:C) designation.
Know when W3 Total Cache gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Unauthenticated network RCE (AV:N/PR:N/UI:N) with full impact and scope change; AC:H retained because a specific input-validation condition must be met.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Arbitrary Code Execution in W3 Total Cache <= 2.9.4 versions.
Executive ViewAI
The W3 Total Cache WordPress caching plugin (versions ≤2.9.4) is vulnerable to unauthenticated remote code execution (CVSS 9.0) that allows attackers to fully compromise any affected WordPress site without credentials or user interaction. With no vendor patch currently available and the plugin widely deployed, this represents an immediate risk to organizational data, system availability, and compliance posture for any entity running affected WordPress instances.
Immediately disable W3 Total Cache plugin on all affected WordPress instances pending patch availability. Deploy Web Application Firewall rules to detect and block exploitation attempts. Restrict network access to WordPress administrative endpoints. Implement file integrity monitoring on WordPress core and plugin directories. Enable comprehensive audit logging for all plugin-related activity and authentication events. Consider temporary deployment of alternative caching solutions to maintain performance while plugin remains disabled.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in W3 Total Cache
View allThe W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.8.
W3 Total Cache plugin for WordPress exposes security tokens to unauthenticated remote attackers through User-Agent heade
pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via
The W3 Total Cache plugin before 0.9.4.1 for WordPress does not properly handle empty nonces, which allows remote attack
The W3 Total Cache WordPress plugin before 2.1.5 was affected by a reflected Cross-Site Scripting (XSS) issue within the
The W3 Total Cache WordPress plugin before 2.1.4 was vulnerable to a reflected Cross-Site Scripting (XSS) security vulne
The W3 Total Cache WordPress plugin before 2.1.3 did not sanitise or escape some of its CDN settings, allowing high priv
Cross-site scripting (XSS) vulnerability in the W3 Total Cache plugin before 0.9.4.1 for WordPress, when debug mode is e
Stored cross-site scripting in the W3 Total Cache plugin for WordPress (all versions up to and including 2.10.6) lets un
Stored Cross-Site Scripting in W3 Total Cache (WordPress plugin) versions up to and including 2.10.5 allows unauthentica
Stored cross-site scripting in W3 Total Cache WordPress plugin (all versions through 2.10.3) allows unauthenticated atta
Stored cross-site scripting in the Bold Grid WordPress plugin W3 Total Cache, affecting every version through 2.10.7, le
EUVD-2026-41365
GHSA-m2v8-v989-39q2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB