# CVE-2026-6670: Media Sync <= 1.4.9 - Authenticated (Author+) Path Traversal via 'sub_dir' and 'media_items' Parameters

> Authenticated attackers with Author-level access can traverse directories to read or modify files outside the intended uploads directory in the Media Sync WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-4j6w-h2q8-35x3

## What is CVE-2026-6670?

CVE-2026-6670 is a medium-severity path traversal vulnerability in erolsk8 Media Sync, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Media Sync plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.4.9 via the 'sub_dir' and 'media_items' parameters. This is due to insufficient validation of user-supplied file paths, which are not checked for directory traversal sequences or restricted to the intended uploads directory. This makes it possible for authenticated attackers, with Author-level access and above, to perform actions on files outside of the originally intended directory.

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

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


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

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

## Is CVE-2026-6670 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6670 is a medium-severity path traversal vulnerability in erolsk8 Media Sync, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6670 in the wild and no public exploit code.

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

## Sources

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

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