# CVE-2026-12514: Shared Files < 1.7.70 - Unauthenticated Limited File Upload

> Unauthenticated attackers can upload files to a public directory and read server paths due to missing capability checks in the Shared Files WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-4qpc-6xpr-g8g2

## What is CVE-2026-12514?

CVE-2026-12514 is a medium-severity missing authorization vulnerability in Unknown Shared Files, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Shared Files  WordPress plugin before 1.7.67, shared-files-pro WordPress plugin before 1.7.70 do not perform a capability check in their file-upload handler, which is registered for unauthenticated users and protected only by a nonce that is output on public pages, so an unauthenticated visitor can upload files to a publicly accessible directory and read the server's absolute path from the response. Uploads are limited to WordPress's allowed MIME types, so executable PHP cannot be uploaded.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12514 is a medium-severity missing authorization vulnerability in Unknown Shared Files, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12514 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-12514/ (Markdown: https://insights.sbomify.com/CVE-2026-12514/index.md)
```

## Sources

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

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