CVE-2025-6722 BitFire <= 4.5 - Unauthenticated Information Exposure
Unauthenticated attackers can read sensitive files like config.ini and debug.log if directory listing is enabled and index.php is missing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-6722?
CVE-2025-6722 is a medium-severity vulnerability in bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security, published on 2 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2025-6722?
How do I fix CVE-2025-6722?
No fix has been published for CVE-2025-6722 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-6722 being exploited?
There is no known exploitation of CVE-2025-6722 in the wild and no public exploit code.
Sources
Also known as GHSA-fv5p-jgq7-gfm9.