BitFire <= 4.5 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 4.6
- Affected Version
<= 4.5- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-6722
At a glance
CVE-2025-6722 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the BitFire Security WordPress plugin, affecting versions <= 4.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.6; sites on affected versions should update now. Disclosed August 2025, reported by Aurélien BOURDOIS (Elymaro).
Vulnerability Overview
The BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.5 via the bitfire_* directory that automatically gets created and stores potentially sensitive files without any access restrictions. This makes it possible for unauthenticated attackers to extract sensitive data from various files like config.ini, debug.log, and more when directory listing is enabled on the server and the ~/wp-content/plugins/index.php file is missing or ignored.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in BitFire Security <= 4.5 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For BitFire Security the fix is 4.6: builds <= 4.5 are affected, anything from 4.6 onward is not.
Remediation
Update to version 4.6, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: BitFire Security 4.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in BitFire Security – Firewall, Malware Scanner, Bot Blocker, Login Protection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C