Quick answers
- Is CVE-2026-17541 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17541 being exploited in the wild.
- How severe is CVE-2026-17541?
- High severity, with a CVSS score of 7.5, published 10 August 2026.
- Which products and versions are affected?
- Bit File Manager before 6.9.1.
- Is there a fix for CVE-2026-17541?
- A patch was published on 2026-08-10: Fixed in version 6.9.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17541 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-17541?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-200) in a REST API route that exposes the file activity log. The `/wp-json/file-manager/v1/logs/all` endpoint fails to verify user authentication or capabilities before returning activity log entries. An unauthenticated attacker can send a POST request with attacker-controlled pagination parameters (pageNo, limit) to retrieve the entire activity log without authentication headers, nonces, or cookies. The response includes file operation details, absolute server paths, user IDs, display names, and timestamps. The flaw affects installations that have run version 6.8.8 or earlier (which created the activity-log table) and have since been upgraded; fresh installs on 6.8.9+ are unaffected as the table is never created due to a separate installer bug. The issue is fixed in version 6.9.1.
Affected products
- Bit File Manager before 6.9.1
Timeline
- 2026-08-04: disclosed
- 2026-08-10: advisory
- 2026-08-10: patched: Fixed in version 6.9.1