CVE-2025-6722: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security
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.
AI Analysis
Technical Summary
CVE-2025-6722 is a sensitive information exposure vulnerability in the BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security WordPress plugin (versions up to 4.5). The plugin automatically creates a bitfire_* directory that contains sensitive files without proper access controls. When directory listing is enabled on the hosting server and the standard index.php file in the plugin directory is missing or ignored, unauthenticated attackers can retrieve sensitive files like config.ini and debug.log. This exposure can lead to unauthorized disclosure of configuration and debugging information.
Potential Impact
An unauthenticated attacker can access sensitive files stored in the bitfire_* directory if directory listing is enabled and the index.php file is missing or ignored. This can lead to disclosure of configuration details and debugging information, potentially aiding further attacks. The vulnerability does not allow modification or denial of service but compromises confidentiality to a limited extent.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should ensure directory listing is disabled on their web servers and verify that the ~/wp-content/plugins/index.php file exists and is properly served to prevent directory contents from being listed. Monitoring and restricting access to the bitfire_* directory can also reduce exposure.
CVE-2025-6722: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-6722 is a sensitive information exposure vulnerability in the BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security WordPress plugin (versions up to 4.5). The plugin automatically creates a bitfire_* directory that contains sensitive files without proper access controls. When directory listing is enabled on the hosting server and the standard index.php file in the plugin directory is missing or ignored, unauthenticated attackers can retrieve sensitive files like config.ini and debug.log. This exposure can lead to unauthorized disclosure of configuration and debugging information.
Potential Impact
An unauthenticated attacker can access sensitive files stored in the bitfire_* directory if directory listing is enabled and the index.php file is missing or ignored. This can lead to disclosure of configuration details and debugging information, potentially aiding further attacks. The vulnerability does not allow modification or denial of service but compromises confidentiality to a limited extent.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should ensure directory listing is disabled on their web servers and verify that the ~/wp-content/plugins/index.php file exists and is properly served to prevent directory contents from being listed. Monitoring and restricting access to the bitfire_* directory can also reduce exposure.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-06-26T14:19:42.461Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 688ddec0ad5a09ad00d2a67a
Added to database: 8/2/2025, 9:47:44 AM
Last enriched: 4/9/2026, 5:47:04 PM
Last updated: 5/9/2026, 1:50:35 AM
Views: 177
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.