# CVE-2026-16292: Frontend File Manager Plugin <= 23.6 - File Metadata Update via CSRF

> Attackers can modify file metadata via CSRF to force file downloads, affecting logged-in users and potentially guests if uploads are enabled.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **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:** 2 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-2rf9-6fhx-g6mg

## What is CVE-2026-16292?

CVE-2026-16292 is a medium-severity vulnerability in Unknown Frontend File Manager Plugin, published on 2 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 Frontend File Manager Plugin WordPress plugin through 23.6 does not perform nonce validation on one of its file-metadata update actions, allowing an attacker to modify the metadata of a logged-in user's uploaded file via a CSRF attack, which can be leveraged to download that file. When guest uploads are enabled, the same action is reachable unauthenticated against any user's file.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-16292 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16292 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16292 is a medium-severity vulnerability in Unknown Frontend File Manager Plugin, published on 2 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16292 exists.

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

## Sources

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

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