# CVE-2026-9282: W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary File Read via 'f_array[]' Parameter

> Unauthenticated attackers can read arbitrary server files via directory traversal in W3 Total Cache when manual minify mode is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-cx46-vqrj-hfqm

## What is CVE-2026-9282?

CVE-2026-9282 is a high-severity path traversal vulnerability in boldgrid W3 Total Cache, published on 11 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The W3 Total Cache plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.9.4 via the setupSources function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires enabling manual minify mode and supplying a manual-format minify filename so that the hash is empty and the f_array[] entries are not overwritten before reaching setupSources().

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-9282 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9282 exists.

Public exploit code:

- W3 Total Cache <= 2.9.4 - Unauthenticated Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-9282.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9282 is a high-severity path traversal vulnerability in boldgrid W3 Total Cache, published on 11 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9282 exists.

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-9282/ (Markdown: https://insights.sbomify.com/CVE-2026-9282/index.md)
```

## Sources

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

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