# CVE-2026-27384: WordPress W3 Total Cache plugin <= 2.9.1 - Arbitrary Code Execution vulnerability

> An attacker can execute arbitrary code on WordPress sites using the W3 Total Cache plugin due to improper input validation.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-g2g2-5q7p-hmf2

## What is CVE-2026-27384?

CVE-2026-27384 is a critical code injection vulnerability in BoldGrid W3 Total Cache, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2026-27384?


## How do I fix CVE-2026-27384?

No fix has been published for CVE-2026-27384 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27384 being exploited?

There is no known exploitation of CVE-2026-27384 in the wild and no public exploit code.

Public exploit code:

- https://github.com/xxconi/CVE-2026-27384 (github_poc): https://github.com/xxconi/CVE-2026-27384

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27384 and fix it if it is affected.

What it is: CVE-2026-27384 is a critical code injection vulnerability in BoldGrid W3 Total Cache, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27384 in the wild and no public exploit code.

Affected product: BoldGrid W3 Total Cache. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27384/ (Markdown: https://insights.sbomify.com/CVE-2026-27384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27384
- OSV: https://osv.dev/vulnerability/CVE-2026-27384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27384/
Summaries are generated and may contain mistakes; the official description above is the record.