TL;DR
Every WordPress site gets probed by bots, and most owners hear about it only when something breaks. A security plugin is the layer that lives inside the site, where it can see changed files, bad plugin code and weak accounts. Wordfence is the one I install, and this post gives the reasons instead of a ranking. It is also not a whole plan on its own, so the post says where it stops and what belongs in front of it.
If you install one security plugin on a WordPress site, install Wordfence. I run it on my own site, on client sites, and on the projects I run now, and when somebody asks me for the best WordPress security plugin, that is the answer they get.
It comes with a caveat most reviews skip. A security plugin is PHP code inside your website, so by the time it says no, the attacker’s request has already reached your server, woken up PHP and been read. The plugin wins the fight and your hosting pays for it. That is not an argument against Wordfence, but about what a plugin is for and what belongs in front of it.
The short answer
Wordfence, for most self-hosted WordPress sites, and the free version is a reasonable start. Three reasons, in the order I weigh them:
- The free version covers the jobs only a plugin can do. It compares your core, theme and plugin files against the originals on WordPress.org and reports what changed, scans for malware, backdoors and SEO spam, limits login attempts, and adds two-factor authentication.
- It is maintained by a company that does nothing else. Wordfence is made by Defiant Inc. in Seattle, about 40 people by its own count, and its vulnerability database is free for anyone to use, including commercially. You are buying into a research team, not a feature list.
- It is in wide use, which matters for a security tool. The plugin directory lists 5+ million active installations, version 9.0.2, last updated 30 September 2026, rated 4.7 from 5,039 reviews (checked 31 October 2026). Wide use means attack data, and attack data is what firewall rules are made from.
WordPress is worth attacking because it is everywhere: 39.5% of all websites, and 58.2% of those whose content management system is known (W3Techs, 31 October 2026). Nobody is hunting your site in particular. They scan everything.
What Wordfence is
Wordfence describes itself as “an endpoint firewall, malware scanner, robust login security features, live traffic views, and more”: four tools in one plugin, plus a data feed that keeps the first two current.
| Part | What it does | Free or paid |
|---|---|---|
| Malware and file scanner | Compares core, theme and plugin files with the WordPress.org originals, scans for malware signatures, backdoors, SEO spam and bad URLs, repairs changed files | Free, scanning every 3 days; paid scans on your schedule |
| Web application firewall | Blocks requests matching known attack patterns, including attacks on vulnerable plugins | Free with rules delayed 30 days; paid in real time |
| Login security | Login attempt limits, two-factor authentication, passkeys, login CAPTCHA, XML-RPC options, blocked admin logins on breached passwords | Free |
| Blocking and rate limiting | Blocks by IP, hostname, user agent or referrer; throttles crawlers and humans | Free |
| Country blocking | Blocks chosen countries from the login page or the whole site | Premium |
| Live traffic | Requests as they arrive, bots included, with reverse DNS and city-level location | Free |
The scanner is the underrated part. Its list covers “over 44,000 known malware variants” by Wordfence’s count, but the file comparison is the better trick: core and every directory plugin has a known-good copy on WordPress.org, so a changed file is a fact rather than a guess.
Is Wordfence a WAF, and where does it sit?
Yes, and the answer to “where” is the whole story. The Wordfence WAF is an endpoint firewall: it runs inside your hosting, as PHP, on the machine being attacked. Wordfence is direct about the trade. It “protects your site at the endpoint, enabling deep integration with WordPress” and, unlike cloud alternatives, “does not break encryption, cannot be bypassed and cannot leak data”.
To get in front of WordPress itself, it asks PHP for help: “the Wordfence Web
Application Firewall is designed to run via a PHP setting called
auto_prepend_file, which ensures it runs before any potentially vulnerable
code runs”. That mode is called Extended Protection. Without it you are on
Basic WordPress Protection, where the firewall loads as an ordinary plugin,
after WordPress has booted, and an attack on a vulnerable plugin that fires
early can be over before Wordfence is awake.
Either way, the request arrived. It spent your bandwidth, your connection and,
in Basic mode, a full PHP startup. On a plan with a handful of PHP workers, a
botnet hammering wp-login.php can take a site down while Wordfence blocks
every attempt. Pair the plugin with an edge firewall and it stops being your
front door;
Wordfence vs Cloudflare has the detail on how
the two layers divide the work.
What a security plugin can do that an edge firewall cannot
This is why you keep the plugin after putting Cloudflare, Sucuri or your host’s firewall in front of it. An edge service acts on requests crossing its network, and these never cross it:
- A changed core, theme or plugin file. It is already on your disk, and only something on the server can compare it with the original.
- Malicious code in a plugin you installed yourself. An abandoned plugin, a nulled premium theme, a backdoor from an earlier break-in.
- Weak accounts and a missing second factor. An edge firewall passes a correct login through, because a correct login looks like a correct login. Two-factor authentication and passkeys live where the login happens.
- What the site does after it answers. SEO spam in your posts, redirects added to the database, a scheduled task that was not there yesterday.
An edge firewall is the gate at the entrance. The plugin is the part that knows what the building should look like inside.
What Wordfence cannot do
Two more limits, on top of the one above.
It cannot fix a flaw below WordPress. When the problem is in PHP itself, the attack can land before any plugin code runs. That happened in October 2026 with the PHP2Shell vulnerabilities, where the only fix was a patched PHP build on the server: the PHP zero-day post has what that looks like in practice and what to ask your host.
It cannot make a free licence current. Wordfence holds new firewall rules and malware signatures back from free sites for 30 days. Set that against Patchstack’s annual report, which puts the weighted median time to mass exploitation for heavily exploited WordPress vulnerabilities at five hours, and says about half of high-impact vulnerabilities were exploited within 24 hours (State of WordPress Security in 2026, covering 2025). A rule that arrives 30 days after the exploit wave is a historical record. Free Wordfence still blocks the huge volume of old, generic attacks, and still tells you when a plugin you run has a published vulnerability. It just will not be first.
Wordfence free vs Premium, and the Wordfence price
Wordfence’s own summary of the split: “This data is delayed by 30 days for our free customers.”
| Plan | Price | What you get beyond the free plugin |
|---|---|---|
| Free | $0 | Firewall, scanner, login security, rate limiting, live traffic, vulnerability monitoring. Rules and signatures delayed 30 days, scan every 3 days |
| Premium | $149 a year, one site | Real-time rules and signatures, the real-time IP blocklist, country blocking, 30 days of audit log, ticket support, scans on your schedule |
| Care | $590 a year, one site | Premium, plus Wordfence installing, configuring and monitoring it for you, an annual audit, and cleanup after an incident |
| Response | $1,250 a year, one site | Care, plus 24-hour incident response with a one-hour response time and a 24-hour time to resolution |
Those are the figures the pricing page listed in late October 2026. Prices change and Wordfence runs sales, so read the pricing page before you buy; older numbers ($119, $490, $950) still circulate in search results.
One more change, if you were counting on the command-line scanner: Wordfence CLI, the open-source Python scanner, “is no longer available for new Free or Premium licenses”, and its free version reached end of life on 14 October 2026.
Is Wordfence Premium worth it?
My rule turns on one number rather than the feature list.
Pay if a break-in would cost you real money or real trust. A shop, a booking system, anything holding customer data. The 30-day gap is the whole argument: the rule for today’s widely exploited plugin vulnerability either reaches you today or next month. Country blocking and the IP blocklist, which Wordfence says covers over 40,000 known threat actors, are extras rather than the reason.
Stay free if the site is a brochure you could rebuild in an afternoon and you update plugins, delete the ones you stopped using, and read the vulnerability alerts the free version sends.
Buy Care or Response if you do not want to be the one who handles it. Both are a service wrapped around the plugin, priced against an agency retainer.
Wordfence alternatives, and what each one actually is
Most comparison posts score these against each other as if they were the same product. The useful question is which class of tool each one is, since that decides what it can see.
| Tool | What it is | Where it runs |
|---|---|---|
| Wordfence | Endpoint plugin: scanner, firewall, login security | On your server, inside PHP |
| Sucuri | Cloud firewall and CDN plus a monitoring and cleanup service | In front of your server, after a DNS change |
| MalCare | Plugin with off-site scanning and one-click cleanup | Scan on MalCare’s servers, firewall and blocking in the plugin |
| Kadence Security (was Solid Security, was iThemes Security) | Login and hardening plugin with a vulnerability scanner | On your server |
| Patchstack | Vulnerability intelligence and mitigation service | Vulnerability data and rules, delivered to the site |
| Jetpack Protect | Vulnerability scanner, with a firewall on paid plans | Scan from Automattic’s service, firewall in the plugin |
| All-In-One Security (AIOS) | Hardening and firewall plugin | On your server, partly through .htaccess |
Sucuri vs Wordfence
Different layers, not competing plugins. Sucuri’s Website Firewall is a cloud service you switch on by changing your DNS records, after which, in Sucuri’s words, “the firewall intercepts and inspects all incoming packets”. That is what Wordfence structurally cannot do, and it gives you none of Wordfence’s view from inside the site. The Security Platform plans were listed at $229, $339 and $549 a year, the firewall with CDN at $9.99 and $19.98 a month, and every platform plan includes unlimited manual malware removal, which is what you are really buying. If cleanup is what you want to outsource, compare the Sucuri platform with Wordfence Care.
MalCare vs Wordfence
MalCare’s idea is that the scan does not run on your server at all: it copies the files to its own servers and scans them there, so your hosting does no extra work, and its free plan scans every seven days. That is a real answer to the complaint that scanning is heavy. Its install base is far smaller than Wordfence’s, and files scanned elsewhere are files that went elsewhere.
Wordfence vs Solid Security
The plugin people search for as Solid Security is now listed in the WordPress directory as Kadence Security, formerly iThemes Security, version 10.0.6 with 700,000+ active installations. It is strongest where it always was: login hardening, two-factor authentication, brute force protection and site scanning, with automated virtual patching in Pro through a Patchstack integration. It has no equivalent of Wordfence’s file comparison. A plugin renamed twice in a few years is also worth weighing when you pick a tool for the next five.
Patchstack vs Wordfence
Patchstack is barely a competitor to a security plugin, which is what makes it interesting. It calls itself an application security platform covering the open-source vulnerability lifecycle: it tracks vulnerabilities, publishes a database and pushes mitigation rules for specific ones to your site. Its pricing page lists Developer at $69 a month billed annually, $828 a year, and no ongoing free plan, so it is built for agencies and hosts. It says nothing about a weak password or a modified core file.
The best free WordPress security plugin
Wordfence, on the free tiers specifically, because of what the others hold
back. All-In-One Security has 1+ million installs and a good hardening set, but
malware scanning and country blocking are Premium and its .htaccess rules do
not apply on NGINX or IIS. Jetpack Protect scans daily for known
vulnerabilities using the WPScan database, and keeps its firewall and malware
scanning for paid plans. Free Wordfence gives you the firewall and the scanner
together, the pair that catches two different kinds of trouble.
How to use Wordfence: the settings that matter
Installing it takes a minute. These five separate a working install from a security badge in your dashboard.
- Turn on Extended Protection. Wordfence calls this optimizing the
firewall. It writes an
auto_prepend_filevalue into.htaccessor.user.iniso the firewall loads before WordPress. Some hosts block.user.iniand have to set it for you, which makes this a support ticket worth opening. Remove the setting before you move hosts or delete the plugin, or PHP goes looking for a file that is gone. - Fix
How does Wordfence get IPsbefore anything else. Behind a proxy or a CDN, Wordfence sees the proxy’s address instead of the visitor’s unless you tell it where to look. The options include PHP’sREMOTE_ADDR(“Very secure if this is compatible with your site”), the CloudflareCF-Connecting-IPheader (“Only use if you’re using Cloudflare”) andX-Forwarded-For(“Only use if you have a front-end proxy or spoofing may result”). Wrong one way, every visitor looks like one address and blocking one attacker blocks everybody. Wrong the other way, a visitor can forge the header. There is a scan check namedScan for misconfigured How does Wordfence get IPs. - Allowlist your own address, if it is fixed. The setting is
Allowlisted IP addresses that bypass all rules. Home broadband addresses change hands, which turns an old entry into a stranger’s free pass, so use it for a static office or VPN address only. - Treat country blocking as Premium and blunt. It blocks the login page or the whole site by country. Read Wordfence’s own warning twice: check the allowed services setting so search engines “may continue to see the site regardless of a crawler’s location”, and “ad services like Google Ads may penalize listings when a country is blocked from the entire site”. Blocking only the login form has almost no side effects.
- Leave rate limiting on, and look at it. One checkbox,
Enable Rate Limiting and Advanced Blocking, gates every throttling and blocking function, country and IP blocking included. The crawler and human thresholds are where you stop a scraper without annoying a reader.
Then spend ten minutes in Live Traffic in the first week. It turns “the internet is scary” into “this is what is hitting my site”, and it shows whether your rate limits are anywhere near reality.
When a WordPress site does not need a security plugin
Two honest cases.
It is not WordPress. A static site has no login, no database and no PHP, so there is nothing for a security plugin to do. This site is static and runs no security plugin at all. If yours is five pages that change twice a year, that is a real option and a bigger upgrade than any plugin.
The host already does it, verifiably. Some managed WordPress hosts run server-level malware scanning, a firewall in front of your site and a hack cleanup guarantee. If yours does all three, a plugin adds overlap and one more thing to maintain. The word carrying the weight is verifiably, so ask in writing:
Do you scan my site’s files for malware and for changed WordPress core files? Do you run a web application firewall in front of my site, and on which plan? If my site is hacked, do you clean it, and is that included?
If the answer is vague, or amounts to “we have a firewall on the network”, you are still responsible for what happens inside the site, and that is where the plugin lives.
Whatever you run, the plugin is one of three things a WordPress site needs: current software underneath it, a firewall in front of it, and backups you have actually restored once.
Related reading
- Wordfence vs Cloudflare: why you want both, the companion post on where each layer sits and what each one can see.
- PHP zero-day (PHP2Shell): updating WordPress or any CMS will not fix it, for what happens when the flaw is below WordPress and no plugin can help.
- How to set up SPF, DKIM, and DMARC for your domain, step by step, the other half of protecting a small site: stopping people sending mail in your name.
Sources
- Wordfence on WordPress.org, the plugin listing and its feature list, written by Wordfence (version 9.0.2, read 31 October 2026). Setting names and the firewall’s description of itself are quoted from the shipped plugin, version 9.0.2.
- Wordfence pricing, plan prices and the free versus paid comparison table, as the page listed them in late October 2026.
- Wordfence CLI, the command-line scanner and its end-of-life notice, as of late October 2026.
- Patchstack, State of WordPress Security in 2026, covering 2025: vulnerability counts and time to exploitation.
- Sucuri Website Firewall, MalCare, Kadence Security, Patchstack pricing, Jetpack Protect and All-In-One Security, each for what it says about itself (read 31 October 2026).
- W3Techs, WordPress usage, survey of 31 October 2026.
Frequently asked questions
Is Wordfence worth it?
For a self-hosted WordPress site, yes. The free version covers the jobs only a plugin can do: comparing your core, theme and plugin files against the copies on WordPress.org, scanning for malware and backdoors, limiting login attempts, and adding two-factor authentication. Wordfence is also made by a company that does nothing else, which is what you are really buying into when you install a security plugin.
Is Wordfence free?
Yes. The plugin in the WordPress directory is free and includes the firewall, the malware and file-integrity scanner, login security with two-factor authentication, rate limiting and live traffic. Wordfence holds back new firewall rules and malware signatures from free sites for 30 days, and keeps the real-time IP blocklist, country blocking and the audit log for paying customers.
Is Wordfence a WAF?
Yes, Wordfence includes a web application firewall, and it runs on your own server rather than in front of it. At its strongest setting, called Extended Protection, Wordfence uses the PHP setting auto_prepend_file so the firewall loads before WordPress does. That is early for a plugin, and still later than an edge firewall, which answers before the request reaches your host at all.
What does Wordfence do?
Four things. It scans your files against the originals on WordPress.org and for malware signatures, backdoors and SEO spam. It runs a firewall that blocks requests matching known attack patterns. It hardens logins with limits, two-factor authentication, passkeys and a CAPTCHA. And it shows you traffic as it happens, so you can see what is hitting the site.
Does Wordfence slow down your website?
It costs something, because it is PHP code that runs on every uncached request and writes to your database. Wordfence publishes a guide to tuning its resource usage, and for busy multisite networks its own documentation suggests turning off Live Traffic, which stops the logging to the database. How much it costs on a given site depends on the host, the traffic and the settings, so treat any single number you read as somebody else's site.
How much does Wordfence cost?
The pricing page listed Free at $0, Premium at $149 a year for one site, Care at $590 a year and Response at $1,250 a year in late October 2026. Premium buys real-time threat data and country blocking; Care and Response buy a security team, with Response promising a one-hour response time around the clock.
Do I need a security plugin if my host has one?
It depends on what the host actually runs, and most hosting pages are vague about it. Ask three questions in writing: do you scan my files for malware and changed core files, do you run a firewall in front of my site, and will you clean the site if it is hacked. A yes to all three with detail behind it makes a plugin optional. A marketing page that says secure hosting does not.
What is the best free WordPress security plugin?
Wordfence. When you compare free tiers, check three things: does it scan for malware as well as for known vulnerabilities, does the firewall work without paying, and is anything time-delayed. Wordfence answers yes, yes, and yes with a 30-day delay on new rules. Most of the alternatives fail one of the first two, which is a bigger gap than a delay.
How often does Wordfence scan?
Free sites get a scheduled scan every three days, by Wordfence's own comparison table, and you can start a scan by hand whenever you want. Paid licences can schedule scans as often as they like. Separately, the firewall and the vulnerability checks work continuously, so a newly disclosed plugin vulnerability does not wait for the next scan.
Why is Wordfence blocking me?
Usually because it is counting your requests against somebody else's address, or because you tripped a rule you forgot you set. Check the How does Wordfence get IPs setting first: behind a proxy or CDN, a wrong value makes every visitor look like one address, so one block catches everyone. Then check your country blocking, your rate limits and your own IP in the allowlist. If you are locked out of the login, use the unlock link Wordfence emails to the administrator address.