Wordfence is one of the best-known security plugins for WordPress: it provides a web firewall, malware scanner, login protection and traffic monitoring. Not every website needs it, and on shared hosting it comes at a cost. Below, we explain when it is worth using and what to look out for if you decide to install it.
The data was measured in October 2026 with the free licence of Wordfence version 9.0.2 on an aWh cPanel hosting test account, with WordPress 7.1, on a website without content. We also tried out the scan, enabling the firewall and removal. The names of the menus and buttons were checked in November 2026 against version 9.1.1.
Do you need this?
The question is: what is already running on your hosting account?
| Security | By default on cPanel hosting | Does Wordfence add it? |
|---|---|---|
| Malware scan of files | ImunifyAV+ on the server (if it finds anything) | Yes, it compares them to WordPress’s own files as well |
| Flagging vulnerable plugins | WP Toolkit | Yes |
| Security settings | WP Toolkit | Partially |
| Restrictions on password attempts | Server-side protection | Yes, at WordPress level |
| Two-step login | None | Yes (Login Security) |
| Web firewall in front of WordPress | None | Yes |
For a simple, regularly updated website on cPanel hosting, what the server provides is usually sufficient, supplemented by basic security settings and a small plugin that offers two-factor authentication. Wordfence is worth considering if you want a web firewall in front of WordPress – for example, for an online shop or a membership site with many users – or if you want to see for yourself what kind of attacks your website is facing. WP Toolkit is only available on cPanel hosting, so when it comes to web hosting, a security plugin may offer more value due to its ability to flag vulnerable plugins and provide WordPress-level protection.
If Cloudflare or another proxy is in front of the website, some of the firewall rules there will override the Wordfence firewall, and the load will not be generated on the hosting server either.
Installation
- In the admin interface, select Plugins › Add Plugin, search for Wordfence, install it and activate it. You can also do this via the WP Toolkit or the command line:
wp plugin install wordfence --activate. - After activation, the plugin displays this message: You must install a license to continue using Wordfence. Registration is required even for free use. With the RESUME INSTALLATION button and then the GET YOUR WORDFENCE LICENSE button, you can request a licence on the Wordfence website.
- Enter the key you received by clicking the Install an existing license link: the Email field takes the recipient of the alerts, the License Key field the key; then click the INSTALL LICENSE button. A successful installation is confirmed by the Free License Installed message. Wordfence asks for each installation to have its own key.
- Please provide an email address that you check regularly, as the plugin will send alerts to this address.
The plugin’s menu appears in the left-hand sidebar: Dashboard, Firewall, Scan, Tools, Audit Log, Login Security, All Options, Help.
The first scan
On the Scan page, the START NEW SCAN button starts the scan. On our test website without content, it checked 4,433 files, 3 plugins, 3 themes and 414 URLs in 21 seconds. Its only finding, of low severity, was that it had skipped two paths in the malware scan because of the settings; this does not indicate an infection. On a website with many images and plugins, the scan takes much longer.
In the free version, malware signatures are updated with a 30-day delay (Signature updates delayed by 30 days), and the real-time IP blocklist and the reputation checks (Spamvertising Checks, Spam Check, Blocklist Check) are not available.
Enabling the firewall
The firewall starts in Learning Mode, set to seven days in our test. During this time, it only observes the website’s normal traffic to learn it, and does not block anything: in our test, even the attack patterns got through. Before the week is over, go through the website’s important functions: logging in, the forms and the checkout. Then, in the settings of the Firewall page, switch to Enabled and Protecting mode under Web Application Firewall Status, if automatic switching is not enabled.
The default Basic WordPress Protection level only starts working when WordPress loads. You can enable the stronger Extended Protection mode with the OPTIMIZE THE WORDFENCE FIREWALL button:
- The wizard (Optimize Wordfence Firewall) detects the server; on the aWh cPanel server, LiteSpeed/lsapi was preselected, so leave it as it is.
- Download the two backups with the DOWNLOAD .HTACCESS and DOWNLOAD .USER.INI buttons. The CONTINUE button only becomes active after that.
- A successful setup is confirmed by the Installation Successful message.
The wizard creates the wordfence-waf.php file in the website’s root directory and writes a # Wordfence WAF block into the .htaccess and .user.ini files. In our test, the firewall then rejected the directory traversal and script injection patterns with a 403 error and the message A potentially unsafe operation has been detected, while normal requests got through. A simple SQL injection pattern, however, got through because it did not match any rule, so the firewall is no substitute for updates.
What to watch out for with Extended Protection
We observed the following in our own tests:
- Do not delete the
wordfence-waf.phpfile. If the file is missing but the configuration still references it, the entire website will return a 500 error. If this happens, restore the file or remove the# Wordfence WAFblock from the.htaccessfile. - Restoring the
.htaccess_file silently disables the firewall. If you reset the file to its default state, the website will continue to function without errors, but the firewall will not start running early enough, so you will need to run the wizard again. - Migration: the block contains the full path of the file. Before migrating the site or changing folders, turn it off with the REMOVE EXTENDED PROTECTION button, and turn it back on with the wizard afterwards.
How many resources does it use?
Data measured from the test website without content:
| What we measured | Result |
|---|---|
| Time elapsed until the first byte of the homepage | Off: approx. 0.10 s, on: approx. 0.15 s, in Extended Protection mode: approx. 0.17 s |
| The size of the plugin | 22 MB |
The wp-content/wflogs folder |
8.3 MB, immediately after switching on |
| New database tables | 26 |
| New scheduled tasks | Hourly and daily runs |
This isn’t much on an empty website, but the plugin runs with every request, and a full search reads a large number of files. On shared hosting, this may hit resource limits and cause a 508 error. Therefore:
- Scan: in the Performance Options section of the All Options page, enable the Use low resource scanning setting. The scan takes longer but puts less load on the hosting. If you can, schedule scans for periods of low traffic.
- Live Traffic: keep it limited to security events. Logging all traffic writes to the database continuously, so only turn it on for short troubleshooting sessions.
- One plugin is enough: do not use two firewall security plugins at the same time, as they will conflict and place a double load on the hosting.
Behind Cloudflare
If Cloudflare is in front of the website and Wordfence misidentifies the visitor’s address, you may see the proxy’s IP address instead of the visitor’s, so a single block could lock out every visitor. Set the correct source in the How does Wordfence get IPs setting on the All Options page, and check your own IP address on the Tools › Live Traffic page.
If you have locked yourself out
If Wordfence is blocking your own IP address, or if the admin interface fails to load due to your firewall, you can disable it by renaming the plugin folder in File Manager or via FTP: for example, change wp-content/plugins/wordfence to wordfence-ki. Via SSH: wp plugin deactivate wordfence. Afterwards, please refer to the article on firewall IP blocking if the server’s firewall is also blocking your address.
Removal
A standard removal leaves a lot behind. In our test, after deleting the plugin, all 26 tables, the 8.3 MB wflogs folder and some settings remained. Therefore, please proceed in the following order:
- If you have used Extended Protection mode, click the REMOVE EXTENDED PROTECTION button in the firewall settings, download the two backups and click the CONTINUE button. The change can take up to 5 minutes to take effect; don’t delete the plugin until then.
- In the General Wordfence Options section of the All Options page, enable the Delete Wordfence tables and data on deactivation setting and save it.
- Disable and then delete the plugin.
- Delete the remaining
wordfence-waf.phpfile from the website’s root directory.
This way, in our test, the wflogs folder disappeared and four of the 26 tables remained: the tables with the wfls_ prefix belong to Login Security, and a few settings also remain in the database. They don’t run, they just take up space. On the Settings tab of the Login Security page, Delete Login Security tables and data on deactivation removes these too: in a test in November 2026, with both settings enabled, no tables remained, only three tiny settings (wordfence_installed, wf_plugin_act_error, wfls_last_role_change). You can also delete the leftovers in phpMyAdmin.
You can find further WordPress security measures in our practical checklist.