CVE-2026-17540
Bit File Manager lets subscribers read and delete files in the WordPress root
WPScan says the Bit File Manager WordPress plugin (slug file-manager) before 6.9.1 does not properly authorise its file commands. Any logged-in user, even a Subscriber, can read and delete files under the WordPress install directory, including wp-config.php. Fixed in 6.9.1 on 3 August 2026. CVSS 3.1 8.8 from CISA-ADP. Not in CISA KEV. The WPScan advisory includes a PoC.
By ThreatWire Desk · Published 10 Aug 2026 · Updated 26 Oct 2026
- CVSS
- 8.8
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Class
- Info disclosure
- Status
- PoC Available
- KEV
- Not in CISA KEV
- 0-day
- No
- Vendor
- Bit Apps
- Products
- Bit File Manager (WordPress plugin, slug file-manager)
- Affected
- All versions before 6.9.1, per WPScan and the CVE record. Requires a logged-in account with at least the Subscriber role. Wordfence, which tracks the same flaw as CVE-2026-15991, lists 6.0 to 6.9.
- Fixed
- 6.9.1, tagged on WordPress.org on 3 August 2026. The current release is 6.9.2 (2 September 2026).
- CWE
- CWE-284
- Published
- 10 Aug 2026
- Updated
- 26 Oct 2026
The status above is the claim. Links do not upgrade it.
Timing note: the fix shipped on 3 August 2026 and WPScan published on 4 August. The CVE record followed on 10 August. This is not a new disclosure.
CVE-2026-17540 is an access control flaw in Bit File Manager, a WordPress plugin by Bit Apps. On WordPress.org it is listed as "File Manager" under the slug file-manager, with 10,000+ active installations. It is a different plugin from WP File Manager.
WPScan, the CVE Numbering Authority, says versions before 6.9.1 do not properly authorise their file management commands. Any logged-in user, such as a Subscriber, can read and delete files under the WordPress installation directory. WPScan says this can expose the site's configuration secrets and cause a denial of service. CWE-284.
The flaw is not unauthenticated. WPScan says a logged-out request gets nothing. It also says reads stay inside the WordPress directory and that the researcher did not achieve code execution. The readable files include wp-config.php, with the database credentials and the authentication keys and salts.
The CVE record carries a CVSS 3.1 8.8 (High) score added by CISA-ADP. WPScan shows the same 8.8. The full vector is in the CVSS field. NVD published the entry on 10 August 2026, marks it Deferred, and has no score of its own. Patchstack rates it 8.1.
Wordfence tracks the same flaw as CVE-2026-15991, published on 6 August 2026, CVSS 8.8, CWE-862. It lists versions 6.0 to 6.9 and says deleting the right file can lead to code execution. The plugin changelog for 6.9.1 credits both researchers, daroo (Wordfence) and Artus KG (WPScan).
The fix is 6.9.1, tagged on WordPress.org on 3 August 2026. The current release is 6.9.2. The WPScan advisory includes a proof of concept. CISA has not added the CVE to the KEV catalog (catalog 2026.10.23, checked 26 October), and no source reports exploitation in the wild. This record does not reprint requests or payloads.
Read the full explainer.
Sources
- Vendor advisory
- CVE.org record
- NVD entry
- Bit File Manager on WordPress.org (changelog)
- WordPress plugin changeset 3632660 (6.9.1)
- Wordfence Intelligence (CVE-2026-15991, same flaw)
- CVE.org record CVE-2026-15991
- Patchstack advisory (CVE-2026-17540)
- GitHub Advisory Database GHSA-mr78-php7-96p9
- CISA KEV catalog
Related on ThreatWire
- NewsBit File Manager flaw lets any subscriber read wp-config.php, CVE-2026-17540
- CVE recordCVE-2026-14378: DevKit Pro unauthenticated admin takeover via revert_switch
- CVE recordCVE-2026-12227: Visual Composer unauthenticated local file inclusion
- CVE recordCVE-2026-15748: Forminator Forms unauthenticated arbitrary file upload