# CVE-2026-107321: W3 Total Cache < 2.10.6 - Author+ Path Traversal via CDN Media Library Import

> Authors can plant files that, when imported by admins, expose arbitrary server files to unauthenticated users via path traversal.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-445r-vc94-h34g

## What is CVE-2026-107321?

CVE-2026-107321 is a medium-severity path traversal vulnerability in Unknown W3 Total Cache, published on 10 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The W3 Total Cache WordPress plugin before 2.10.6 does not confine a media-import file copy to the document root, nor enforce an effective file-type restriction on it, allowing users with the Author role or higher to plant content that, once an administrator runs the import, copies an arbitrary server-readable file into a publicly served directory, exposing it to unauthenticated retrieval.

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

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


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

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

## Is CVE-2026-107321 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107321 is a medium-severity path traversal vulnerability in Unknown W3 Total Cache, published on 10 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-107321 in the wild and no public exploit code.

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

## Sources

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

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