# CVE-2026-17540: Bit File Manager < 6.9.1 - Subscriber+ Arbitrary File Read and Deletion via Connector Command Request-Source Mismatch

> Authenticated subscribers can read and delete arbitrary files in the WordPress installation, leading to information disclosure and denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-mr78-php7-96p9

## What is CVE-2026-17540?

CVE-2026-17540 is a high-severity missing authorization vulnerability in Unknown File Manager, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The File Manager WordPress plugin before 6.9.1 does not properly authorise its file management commands, allowing any authenticated user, such as a subscriber, to read and delete arbitrary files under the WordPress installation directory, which could lead to the disclosure of the site's configuration secrets and to denial of service.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-17540 being exploited?

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

Public exploit code:

- WordPress Bit File Manager < 6.9.1 - Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-17540.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17540 is a high-severity missing authorization vulnerability in Unknown File Manager, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17540 exists.

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

## Sources

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

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