# CVE-2026-17541: Bit File Manager < 6.9.1 - Unauthenticated File Activity Log Disclosure

> Unauthenticated attackers can access the file activity log via a REST API route, revealing file operations, paths, and user names.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 10 Aug 2026
- **Updated:** 10 Aug 2026

## What is CVE-2026-17541?

CVE-2026-17541 is a high-severity missing authorization vulnerability in Unknown File Manager, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The File Manager WordPress plugin before 6.9.1 does not have authorisation checks on one of its REST API routes, allowing unauthenticated users to read its file activity log, disclosing the file operations performed on the site, the paths involved and the name of the user who performed them.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-17541 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17541 is a high-severity missing authorization vulnerability in Unknown File Manager, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17541 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-17541/ (Markdown: https://insights.sbomify.com/CVE-2026-17541/index.md)
```

## Sources

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

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