# CVE-2026-12513: Shared Files < 1.7.68 - Unauthenticated Arbitrary File Deletion via Path Traversal

> Unauthenticated attackers can delete arbitrary server files via path traversal in Shared Files plugin, causing denial of service or site takeover.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-h23j-55hj-5495

## What is CVE-2026-12513?

CVE-2026-12513 is a medium-severity path traversal vulnerability in Unknown Shared Files, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Shared Files  WordPress plugin before 1.7.67, shared-files-pro WordPress plugin before 1.7.68 do not properly sanitize a file path taken from a frontend file submission and their single-pass traversal filter is bypassable, allowing unauthenticated users to store a path that points outside the uploads directory. When the corresponding file entry is later permanently deleted, an arbitrary file on the server (such as wp-config.php) is deleted, leading to denial of service and potential site takeover.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-12513 being exploited?

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

Public exploit code:

- CVE-2026-12513 Vulnerability Advisory & PoC — Discovered by Huynh Kien Minh (MinhHK). (github_poc): https://github.com/MinhHK68/CVE-2026-12513

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12513 is a medium-severity path traversal vulnerability in Unknown Shared Files, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-12513 in the wild and no public exploit code.

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

## Sources

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

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