Only patented WordPress Firewall locks your php files from malware. Complete protection from bots.
Recover hacked sites. Identify plugin vulnerabilities, 100 MFA, SQLi, XSS, CSRF, LFI firewall
Website security that works. Don’t just scan for malware. Stop it from ever infecting your site.
BitFire integrates your website and server operating system to make website hacks, redirect attacks and account takeover impossible.
Don’t just scan for attacks after they happen; actively prevent them.
There are many Web Firewalls available. Only BitFire has 100% Free bot Blocking, Site Restore, Vulnerability Detection, File Locking, Redirect Protection, and a money-back guarantee for PRO customers.
BitFire brings new security capabilities to your website you won’t find anywhere else.
In addition to the standard Protection offered by similar solutions, BitFire has 4 unique features that, when activated, make your site impervious to attack.
- File Protection – Write Lock your files to prevent any attack from modifying your plugins or core files.
- Bot Protection – 99% of hacks are automated. BitFire blocks all automated requests and only allows approved search engines and tools.
- Redirect Protection – Prevent redirect attacks by enforcing only content from approved sites with dynamic Content Security Policy.
- Multi-Factor Authentication – Prevent account takeover with multi-factor authentication. Receive notification of all login attempts.
Vulnerability Detection – Automatically check all of your plugins and themes against a database of over 3,500 known wordpress vulnerabilities.
Up to 50x faster than the competition
- More 0-day protections than anyone
- Full guaranteed Protection in less than 2 milliseconds.
Protect yourself from 0-day threats with security processes, not just known signatures.
Privacy / Monitoring / Data Collection
Privacy. We take privacy very seriously. BitFire inspects all traffic going to the webserver and takes care to filter out any potentially sensitive information by replacing it with redacted. This can include information like passwords, credit card numbers, etc. The config.ini file includes a list of common sensitive field names under the „filtered_logging“ section. These fields are immediately filtered and can not be included in any logging or error reporting. You can add additional fields to filter in the config file by adding a line „filtered_logging[field_name] = true“ and replacing „field_name“ with the name of the desired parameter to filter.
BitFire includes error monitoring. While we strive to make BitFire as robust as possible, sometimes unforeseen things happen. BitFire includes error handler which monitors it’s operation. In the event an error is detected only in the BitFire software; including during install, an alert can be sent to BitFire’s developer team. The development team monitors these errors in real time and includes fixes for any detected errors in each new release. This feature includes sending basic server info in the error report to help diagnose the problem. You may opt in/out on the setting page.
Plugin usage. You can help the development team improve the functionally by opting in to use the usage monitoring. This adds a counter to send button clicks to help the development team understand which features are used by customers and how often. Default off.
Updates. Four times a day BitFire will request the latest signatures from the BitFire signature API. These signatures are sent over SSL(TLS) and encrypted specifically for each client site. In addition bitFire also sends a list of installed plugins and version numbers to compare against recently posted security vulnerabilities.
Malware scanning. When bitfire scans your website for malware it creates signatures for every file on your site. It then compares these signatures against a database of over 20 million WordPress signatures to ensure your file integrity. To do this, BitFire will send the signature values (hashes) of every file to the bitfire malware api. In addition to this, any found differences are compared with the official WordPress code hosted at wordpress.org. When malware is detected it’s signature added to BitFire’s growing malware database for improved detection.
PRO / PREMIUM. The PRO version of BitFire is limited to 10,000 page views per day. If you are using the PRO version and you regularly exceed this usage, a notice will be sent to you and BitFire requesting a license upgrade. This data includes approximate daily usage per domain.
- Install this plugin via WordPress plugin installer.
- In your Plugin Dashboard, click „Activate Plugin.“
- Click on „BitFire Admin“ from wp-admin.
Can BitFire block bots and automated attacks?
Do I have to buy it?
BitFire includes a complete standard firewall, malware scanning, vulnerability detection and unbreakable bot blocking for free. Additional features, including File Write Locking, Redirect Protection, Automated Malware Recovery, and Multi-Factor Authentication, require paid PRO or PREMIUM versions. https://bitfire.co/pricing
How does Redirection Protection work?
Does BitFire prevent Cross-Site Scripting (XSS)?
BitFire includes outstanding XSS protection, including HTTP headers and content filtering for persistent, reflected, and DOM-based XSS attacks.
Does BitFire block SQL Injection attacks (SQLi)?
Yes. BitFire has advanced SQL parsing similar to MySQL syntax parsing and can understand SQL queries regardless of encoding, injected comments, and other evasion techniques.
Why shouldn’t I use WordFence?
If you use WordFence, you should only use the paid version. WordFence has a team monitoring emerging WordPress vulnerabilities and writing custom rules to block specific exploits. They are very good at it and run a great blog on their work. Paying customers receive these virtual patches as soon as they are available. Free customers receive the patches 30 days later. If your website is vulnerable, it is almost guaranteed to be hacked before the patch is available to free customers. Don’t leave your site at risk.
Why is BitFire better than WordFence?
„Better“ can be subjective. Our generic attack detection is on-par, if not better. WordFence does not have browser or bot network authentication and can not block many automated attacks. BitFire is the only WordPress plugin offing operating system integrated file-locking and browser enforced redirect protection.
We are also definitely FASTER. WordFence typically doubles page load time, adding 100-200ms to every request on typical dedicated T4 small/medium AWS servers, more for shared environments. BitFire runs under 5ms on similar AWS hardware and near 10ms on shared environments.
We believe BitFire is the only plugin that can effectively protect WordPress sites – and is the only one with a 100% money-back guarantee for paid customers (up to 12 months effective).
There are no reviews for this plugin.
Þátttakendur & höfundar
“BitFire” er opinn hugbúnaður. Eftirfarandi aðilar hafa lagt sitt af mörkum við smíði þessarar viðbótar.Höfundar
- Added plugin vulnerability notifications. These will check over 3500 active CVE advisories
for any known security issues in your plugins or themes
- Improved upgrade process which could forget some settings on upgrade
- Fixed a possible rare false positive on base64 encoded data
- Improved learning mode to find more false positives
- Fixed a warning on PHP 8.x with undefined variable for alerts from IPs with no associated country
- Fixed a bug which incorrectly reported the currently viewed alert page number range on the dashboard screen
- Several bug fixes
- Improvements to malware scanning, added additional files to scan list
- Fixed bug adding additional allowed domains on settings page
- Implemented setup wizards and online help functions.
- Added auto-learning exceptions for new installs to prevent possibility of false-positives..
- Workflow and usability improvements
- fixed an issue that could cause false positive when non administrators
were editing posts. This check has been expanded to authors as well.
- fixed an issue that was causing extra padding in config.ini files
- added support for auto-discovering bots to whitelist
- reduced the maximum size of saved blocked data
- fix for WordPress source code path resolution
- use CMS default script inclusion system for admin pages
- added initial support templates for custom CMS
- refactored escaping on MFA page
- fixed an issue which could allow admin requests to be rate limited
- refactored malware scanner to support custom CMS
- added support for redirect url on MFA login page
- fixed issue with MFA login submission
- added support for Content Security Policy WordPress integration
- WordPress MFA login support complete
- PHP file write blocks are now logged in the dashboard
- improved support for alternate content management systems
- removed direct $_SERVER, $_GET, $_POST access and replace with filter_input
- fixed issue that could cause malware download to fail with expired access token
- improved install logging
- additional tests for installation procedure
- added SQL auditing feature. Currently this is an advanced toggle only available
by editing the config.ini. Planned features: SQL Injection Detection, CC data
access, replay log for DB restores
- namespaced all defines to prevent any possible name collisions
- added WordPress plugin and theme enumeration blocking
- refactored several echo lines to remove dead code and xss encode on the same line
- added fix for a bug in php >=8.0 <= 8.1 where splat operator on variables containing :
would be incorrectly interpreted by PHP 8.0 as a named operator.
- added support for cloudflare real connecting IP
- plugins not registered at wordpress.org are now rolled into a single malware line
- upgraded bootstrap and chart.js to latest stable releases
- refactored all API methods to be pure and testable
- refactored malware detection to allow detecting malware on non-WordPress installs
- updated all WordPress path resolutions
- added code to ensure config.ini is not web readable even when .htaccess is disabled
- INI settings: reset realpath.cache_size to system size when used with openbase_dir
- special handling of DOCUMENT_ROOT for WordPress
- improvements to installing always on protection on Nginx systems
- make config.ini unreadable even on systems that do not support .htaccess
- added additional WordPress abstractions as requested by WordPress team
- upgraded bootstrap css files
- abstracted wordpress plugin with pure implementations and additional unit tests
- refactored several functions with pure implementations and added unit tests
- refactored views to use new template system
- refactored wordpress integration to use standard plugin architecture
- removed dead code
- removed a warning for php 8.1
- Added support to enable always-on from settings page
- Added support for WordPress Engine
- Fixed bug where rotating encryption keys would prevent new signatures from downloading for up to a day
- Improved support for PHP 8.0
- improved settings page
- improved malware scanner
- additional whitelist SEO bots
- improved auto-detection of server support
- First public release of BitFire WordPress security plugin