Plugins · bitfire · data as of 2026-11-04
Is BitFire Security safe? Known vulnerabilities and latest version
- Latest version
- 5.2.4
- Last updated
- 2026-09-24
- Active installs
- 300+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Free WordPress firewall, bot blocking, login protection, and malware scanning. See suspicious traffic and investigate threats from your dashboard. — by Cory Marsh
What to do
- Update to the latest version (5.2.4). Anything older than 5.0.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get bitfire --field=version shows what you run; wp plugin update bitfire updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 8.6 CVE-2026-56035 · published 2026-06-26
Security issue in BitFire Security (5.0.3 and older)
- Affected
- 5.0.3 and older
- Fixed in
- 5.0.4
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Multiple Vulnerabilities in BitFire Security <= 5.0.3 versions.
medium 5.3 CVE-2025-6722 · published 2025-08-02
Information disclosure in BitFire Security (4.5 and older)
- Affected
- 4.5 and older
- Fixed in
- 4.6.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
Recent activity
- 2026-09-24 — latest release on wordpress.org (5.2.4).
- 2026-06-26 — Security issue disclosed (CVE-2026-56035), fixed in 5.0.4.
- 2025-08-02 — Information disclosure disclosed (CVE-2025-6722), fixed in 4.6.1.
Get an email when BitFire Security has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for BitFire Security (bitfire) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Sensitive data exposure (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/bitfire (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/bitfire"><img src="https://laskyr.com/plugins/bitfire/badge.svg" alt="BitFire Security vulnerability status"></a>