Most people shopping for a WordPress security plugin ask which one is best. That question assumes the products compete, and mostly they do not. A firewall, a malware scanner, a vulnerability feed, a login guard, an activity log and a backup system are different jobs, and the tools on this page cover different combinations of them. The useful question is which of those jobs nobody is doing on your site today.
The single most important idea here is this: buy for the layers you are missing, and run exactly one firewall. Two plugins that both filter requests, edit .htaccess, lock out IP addresses and scan files will argue with each other. You get duplicate alerts, administrators locked out of their own dashboard, slow admin screens and a false feeling of coverage. Layers should stack. Overlap should not.
Start with how sites actually get compromised, because that tells you which layers earn their keep. In most cleanup stories the entry point is one of three things: a known flaw in a plugin or theme that was published weeks earlier and never patched on that site, a password that was reused or stolen and had no second factor behind it, or abandoned or pirated software that nobody maintained. Very few begin with a clever attack on WordPress core. That is why the least glamorous layers, patching, vulnerability alerts and two-factor login, protect more sites than any scanner does.
Here are the layers this page uses, with the question each one answers:
- Firewall: can this request reach WordPress at all? It can run inside WordPress as an endpoint plugin, or sit in front of your server as a DNS-level or cloud WAF.
- Vulnerability intelligence and virtual patching: is something I have installed known to be exploitable, and can the exploit be blocked before I get a chance to update?
- Malware scanning and cleanup: is something malicious already on the site, and who removes it?
- Login hardening and two-factor authentication: can a guessed or stolen password alone get someone in?
- File integrity: did a core, plugin or theme file change when nobody released an update?
- Activity logging: who changed what, when and from where?
- Backups and recovery: if every other layer fails, how quickly can you return to a known good state?
The eight products here map onto those layers unevenly, which is the point. Wordfence Security is the broad endpoint suite: firewall, scanner and login security in one plugin. Patchstack does one thing, vulnerability intelligence with virtual patching. MalCare is a cloud-assisted malware scanner with automated cleanup. Solid Security is strongest on login hardening and site hardening. Sucuri combines a free monitoring plugin with a paid cloud firewall and a cleanup service. WP Activity Log is an audit trail and nothing else. Cloudflare WAF is the non-plugin alternative that filters traffic before it reaches your server. Jetpack Protect is a light, free-to-start vulnerability checker with paid scanning above it.
Every layer also has a limit, and a good setup is built around those limits. A firewall cannot stop a legitimate administrator whose password was stolen if nothing asks for a second factor. A scanner finds trouble after it has landed. A vulnerability database cannot know about a flaw nobody has reported yet. Two-factor login does nothing against a plugin bug that skips the login screen entirely. An activity log records the break-in but does not prevent it. A backup restores your files but leaves the hole open. When you read each product below, ask what it cannot do as carefully as what it can.
Your hosting plan matters more than most reviews admit. Many hosts already run a server-level firewall, malware scanning, account isolation and daily backups. If yours does, paying for the same layer inside WordPress buys little, while the layers hosts rarely provide, such as telling you which plugin on your site is vulnerable today, may be exactly what you lack. Before you buy anything, find out what your host really does and what it leaves to you.
Performance and false positives are the hidden price. An endpoint firewall runs PHP on every uncached request. A file scanner reads your disk, and on cheap shared hosting a full scan can slow the whole site or time out. A firewall rule that is too eager will block a payment webhook, a mobile app or your own editor. The cost of getting that wrong is not abstract: a blocked checkout loses orders while looking, to you, like nothing is wrong. Each product section says where that friction tends to appear, and the testing method near the end shows how to find it before your customers do.
One honest note about this page. WPresident has not run formal tests of these products. The fit scores are an editorial assessment based on documented behaviour and the way these products are widely described and used, so treat them as a starting point for your shortlist, not a measurement. Plans, tiers and bundled features change often, so we describe pricing as a model in words and tell you what to verify on each vendor’s own page before you pay.
Key takeaways
- Security plugins cover different layers, so the real decision is which layers you are missing, not which brand wins.
- Run one firewall only: either an endpoint plugin such as Wordfence Security, or a DNS-level WAF such as Cloudflare or the Sucuri firewall, and stack the other layers around it.
- Most compromises begin with a known plugin flaw, a weak or reused password, or abandoned software, so vulnerability alerts, virtual patching and two-factor login usually matter more than another scanner.
- A scanner finds damage after it happens and a log explains it afterwards: neither one blocks anything, and neither replaces tested backups.
- Check what your host already provides before paying twice, and confirm that any cloud firewall is the only way to reach your origin server.
- Every layer has a performance and false-positive cost, so test checkout, forms, webhooks and admin screens after turning one on, and test that alerts really arrive.
- Decide your incident-response order before you need it: contain, preserve, find the entry point, clean, rotate credentials, restore, then close the hole and monitor.
Find your match in 60 seconds
Answer a few questions about your site and the layers you lack, and we will rank the products that fit your situation.
This quiz needs JavaScript. Without it, use the comparison table and the situations below.
The shortlist at a glance
Fit ratings are an editorial assessment from each product’s documented behaviour and typical use, on a 0 to 5 scale. They are not lab results. Click a column heading to sort. Highlighted cells are the strongest in that column.
| Product | Easy for beginners | Blocks attacks before they run | Malware scanning and cleanup | Vulnerability intelligence | Login hardening and 2FA | Activity and change visibility | Light on server resources | Multi-site and agency fit |
|---|---|---|---|---|---|---|---|---|
| Wordfence Security Freemium plugin | ||||||||
| Patchstack Freemium service with a plugin | ||||||||
| MalCare Freemium plugin and cloud service | ||||||||
| Solid Security Freemium plugin | ||||||||
| Sucuri Free plugin plus paid cloud firewall and cleanup service | ||||||||
| WP Activity Log Freemium plugin | ||||||||
| Cloudflare WAF DNS-level cloud firewall (not a plugin) | ||||||||
| Jetpack Protect Freemium plugin |
| Product | Type | Pricing model | Best for |
|---|---|---|---|
| Wordfence Security | Freemium plugin | Free plugin with paid tiers sold as annual licenses per site, where paying mainly buys faster threat updates and extra features; check the vendor page for what each tier includes | A single site or a small set of sites on a server you control that needs an endpoint firewall, a malware scanner and two-factor login in one plugin. |
| Patchstack | Freemium service with a plugin | Free tier for vulnerability monitoring and paid tiers, usually priced per site or per bundle of sites, where virtual patching and extra features sit in the paid plans; verify the current structure | Anyone who updates on a schedule rather than instantly and wants early warning and a stopgap block when a plugin flaw is published. |
| MalCare | Freemium plugin and cloud service | Free scanning with paid plans per site or per bundle of sites, where automated cleanup and firewall features sit in paid tiers; confirm the tier structure on the vendor page | A site owner or agency that wants malware detection that does not load the hosting server and a cleanup button instead of a manual investigation. |
| Solid Security | Freemium plugin | Free Basic version and a paid Pro version sold as annual licenses by number of sites; check the vendor page for which features sit in which edition | Sites where the main risk is accounts and the dashboard, such as membership sites and teams with many editors, and owners who want a guided hardening checklist. |
| Sucuri | Free plugin plus paid cloud firewall and cleanup service | A free monitoring plugin and a paid platform sold as plans per site, covering a cloud firewall and managed cleanup; plans differ in how much cleanup and which firewall features are included, so verify on the vendor page | A site that wants traffic filtered before it reaches the server and a team to clean and recover it after an infection, and whose owner can change DNS. |
| WP Activity Log | Freemium plugin | Free version with a paid Premium version sold as annual licenses by number of sites; alerts, reports, extra plugin support and external log storage are generally in paid tiers, so verify what each edition includes | Sites with several editors, contractors or administrators, and anyone who needs to know who changed what for accountability, client reporting or incident investigation. |
| Cloudflare WAF | DNS-level cloud firewall (not a plugin) | Account plans by tier with a free level and paid levels; the web application firewall, rate limiting and bot features available depend on the plan, so verify the current feature list per tier on the vendor page | Sites where you can change DNS and want attack traffic stopped before it reaches the server, including stores, busy sites and agencies running many domains. |
| Jetpack Protect | Freemium plugin | Free plugin with paid tiers that add malware scanning and further security features; the free tier is limited to vulnerability checks, so verify what each paid tier covers | A site owner who wants free, low-effort awareness of known plugin and theme vulnerabilities from a major vendor, without installing a full security suite. |
How to choose: what actually matters
Where the firewall sits
A firewall is either inside WordPress or in front of it, and that one fact decides most of what it can and cannot do. An endpoint firewall is PHP code that runs on your own server. It knows whether a visitor is logged in and can inspect parameters in context, but it only sees requests that reach PHP, so a fully cached page served by the web server or a CDN never touches it, and a flood of requests still consumes your server before the plugin can say no. A DNS-level or cloud firewall sits in front: traffic resolves to the vendor first, bad requests are dropped at the edge, and your server never sees them. In exchange it cannot see inside WordPress, and it works only if visitors cannot reach your origin server directly.
To check on your own site, look at where your domain’s nameservers or address records point, and ask whether your origin IP address is reachable without going through the vendor. Also ask the endpoint plugin vendor whether it can load before WordPress starts, because that mode covers more code than the basic one.
Vulnerability intelligence and virtual patching
Because known flaws in plugins and themes are the usual way in, the quality of a product’s vulnerability data matters more than how many features appear on its tab list. Judge three things. First, coverage: does it check core, plugins and themes, including premium ones that are not hosted in the official directory? Second, timeliness: how quickly does a newly published flaw show up as an alert on your dashboard? Third, action: does it only tell you, or can it also block exploitation until you can update?
That last capability is called virtual patching. A rule on the firewall recognises the specific request pattern that triggers the flaw and stops it, without touching the vulnerable plugin. It buys time when an update is not out yet or when you cannot apply it without testing. It is not a substitute for updating, and it only covers flaws that have been reported, triaged and turned into a rule. Ask each vendor how rules are written, who writes them, and which tier includes them.
Malware detection method and cleanup
Scanners find malware in three different ways, and the differences explain why two tools can disagree about the same site. Integrity comparison checks core, plugin and theme files against known good originals and flags any difference. Signature matching looks for known malicious code patterns. Behavioural or heuristic checks flag code that does suspicious things, such as decoding hidden strings and then running them. Integrity comparison is precise but only covers software with a known original. Signatures miss new variants. Heuristics catch more but produce more false alarms on legitimate obfuscated code.
Also ask where the scan runs. A scan on your own server uses your CPU and disk. A scan that runs on the vendor’s servers is light for you but means site data leaves your hosting account. Then ask what cleanup means: a button that removes what the tool found, or a person who investigates. Neither one tells you how the attacker got in, and that is the part that stops reinfection.
Login hardening and two-factor coverage
Stolen and reused passwords are among the most common ways into a WordPress dashboard, and a firewall cannot tell a stolen password from the real owner. Look for two-factor authentication that works with an authenticator app, not only email codes, and that can be required for specific roles, such as administrators and shop managers, instead of left as an optional setting nobody turns on. Look for limits on failed attempts per account and per IP, for protection of the XML-RPC and REST endpoints that attackers use to guess passwords in bulk, and for a way to block weak passwords.
Be wary of features that only reduce noise. Moving the login URL or hiding it cuts down log clutter from bots but does not stop a targeted attacker who already has valid credentials. Check what happens when you lose your phone: a recovery path that does not exist will lock you out, and a recovery path that is too easy defeats the point.
File integrity and activity logging
These two layers answer different questions. File integrity monitoring tells you that a file changed on disk, which catches backdoors and edits made outside WordPress. An activity log tells you what happened inside WordPress: a new administrator was created, a plugin was installed, a setting was changed, a user logged in from a new country. During an incident you want both, because the log gives you the timeline and the file check gives you the footprint.
Check four things. Where is the log stored: a log kept only in the same database an attacker just compromised can be edited or deleted, so look for external storage or a forwarding option. How long is it kept, and does pruning delete the evidence you need? Does it send alerts for the few events that really matter, such as a new admin account, instead of emailing every page edit? And how much does it write to your database on a busy site, since logging is not free.
Performance cost and false positives
Every layer costs something. Endpoint firewalls run code on each uncached request. File scanners read thousands of files and can push a small hosting plan past its CPU or memory limit, producing slow pages or killed processes. Activity logs add database writes. Cloud firewalls add a network hop and a new place where a misconfigured rule can silently block good traffic.
False positives are the more dangerous cost because they are quiet. A rule that blocks a payment gateway’s callback does not show an error on your screen. Orders simply stop being marked as paid. Judge each product on whether it has a learning or monitoring mode, per-rule allowlisting, a readable block log that tells you which rule fired, and a way to exempt specific URLs, IP ranges and request types. Then test the flows that matter on your own site: checkout, contact forms, logins, file uploads, REST calls from apps and integrations, and scheduled tasks.
Recovery: backups and incident response
Prevention fails sometimes, so judge what happens next. A security plugin is not a backup, and a backup is not a cleanup: restoring last night’s copy only helps if it predates the intrusion, and an old backup can contain the same backdoor. Look for products that keep or integrate with versioned backups, that tell you when a compromise probably began, and that give you a defined path from detection to a clean site, whether that is a person or an automated tool.
A sound order of operations, whatever you use, looks like this:
- Contain: put the site in maintenance mode or block public access, and change the hosting and admin passwords.
- Preserve: take a full copy of files and database as they are, plus server logs, before you change anything.
- Find the entry point: use logs, file timestamps and the activity log to see what changed first.
- Clean: remove malware and backdoors, or restore a copy you trust, then reinstall core and plugins from clean sources.
- Rotate everything: passwords, salts, API keys, database credentials and any other accounts on the same hosting.
- Close the hole, then monitor closely.
Overlap with hosting-level protections
Before you compare plugins, list what your host already does. Many hosts run a server firewall that blocks common attack patterns, scan for malware at the account level, isolate each site so that a problem on one does not spread to another, apply rate limits to login pages and keep backups. Some include a CDN or a cloud firewall in the plan. A few also warn you about vulnerable plugins.
The risk is double filtering. If the host already runs a WAF and you add an endpoint firewall that rewrites server rules, requests can be inspected twice, blocked inconsistently or logged in two places that disagree. Ask your host three questions in writing: what is blocked before WordPress loads, what is scanned and how often, and what is your responsibility. Then fill only the layers they do not cover. The same applies to a CDN you already use: if it offers firewall rules, decide which tool owns that job.
Fleet management and alerting
For a single site, the alert path is simple: one email address, ideally one that a person actually reads. For an agency or anyone running many sites, the question is whether you can see all of them in one place and tell which ones need attention. Look for a central dashboard, a way to apply the same settings to every site, alerts that include the site name and a clear severity, and a way to hand reports to a client without exposing other clients.
Check how licensing scales, because per-site pricing and bundles behave very differently at ten sites than at one. Also look at what a single sign-in on that dashboard can do: a dashboard that can push changes to every site is a convenient target, so it deserves strong login protection of its own. Finally, decide where alerts go on a holiday weekend, since an unread inbox is the same as having no alerts at all.
Best for your situation
Brochure site whose owner rarely logs in
A five-page site for a local business on managed WordPress hosting. The owner updates plugins when reminded and does not want another dashboard to learn.
Pick: Jetpack Protect
The likeliest problem on a site like this is an outdated plugin with a known flaw. A free, near-zero-configuration vulnerability check addresses that directly and costs almost nothing in server resources. The host already provides a server firewall and backups, so a full suite would mostly duplicate it.
Watch out: Add two-factor login for the one administrator account, and make sure someone reads the email when a flaw is reported, because a free report nobody opens protects nothing.
WooCommerce store with 300 products and daily orders
A store on a VPS where PHP workers are the scarce resource, hit by bots probing the login page and the cart. The owner can change DNS.
Pick: Cloudflare WAF
Filtering at the edge keeps bot traffic and login attacks away from PHP, which is the resource a store cannot afford to waste. Rate limits on the login page and a challenge on the admin area are cheap to add. Pair it with a vulnerability layer and an activity log rather than expecting the edge to cover everything.
Watch out: Create skip rules for payment gateway callbacks, exclude cart and checkout from caching, and lock the origin so attackers cannot bypass the edge.
Membership site with thousands of logged-in users
A paid community with several editors and moderators, where stolen passwords and privileged accounts are the main exposure.
Pick: Solid Security
The risk sits in accounts and roles, which is where its login hardening is strongest: enforced two-factor for privileged roles, attempt limits and password rules. It adds little load on member page views. You still need a firewall layer and vulnerability alerts around it.
Watch out: Do not enforce two-factor for members without a clear support path for lost devices, and avoid running a second plugin that also locks out failed logins.
Agency managing forty client sites
A small agency with a monthly maintenance plan, where an emergency plugin update on a client store is risky and clients expect to hear about problems first.
Pick: Patchstack
The vulnerability layer is the one that decides whether a fleet gets compromised through a plugin flaw, and virtual patching gives you time to test an update on staging. One dashboard across clients, with light server impact, scales better than scanning forty sites on forty small hosting plans.
Watch out: It does not scan for malware or log changes, so pair it with a scanner and an activity log, and agree which person acts on which severity.
A site that was hacked before and will be again if nobody owns it
A lead-generation site cleaned once by a freelancer, then reinfected a month later. The owner wants someone else to handle detection, cleanup and blocklist removal.
Pick: Sucuri
A human-led cleanup service and a cloud firewall address both the infection and the traffic that caused it, and help with blocklist removal addresses the reputation damage. A repeat infection usually means the entry point was never closed, so a team that investigates is worth more than a button.
Watch out: Lock down the origin so attackers cannot bypass the firewall, and still update the vulnerable software, because a cleanup does not fix the original flaw.
Small business site on cheap shared hosting
A shop on an entry-level plan where on-server scans have previously timed out or slowed the site, and the owner is not technical.
Pick: MalCare
Because the analysis runs off the server, scans do not compete with your visitors for CPU and memory. The result is shown in plain language, with a cleanup option if something is found. That matches an owner who wants a clear answer and not a settings page.
Watch out: Take your own backup before any automated cleanup, and check your privacy obligations if the site stores sensitive customer data.
Company site with several editors, contractors and freelancers
Marketing staff, an outside agency and a developer all have administrator or editor access, and nobody can say who changed a page last week.
Pick: WP Activity Log
When many people can change the site, the problem is accountability and early warning for odd changes, not just outside attackers. An audit trail answers who did what and when, and alerts on new administrators or role changes catch compromised accounts quickly.
Watch out: Send the log to external storage if your edition supports it, and tune alerts to the few events that matter so people keep reading them.
Single site on a VPS with no firewall and no control over DNS
A developer-run site where the client controls the domain registrar and will not move nameservers, and the server has no application firewall.
Pick: Wordfence Security
An endpoint plugin gives you a firewall, a scanner and two-factor login without changing DNS, and extended protection means the firewall can load before WordPress starts. The free tier is a reasonable starting point and the blocking log helps you tune.
Watch out: Remember that cached pages skip PHP and so skip the firewall, watch scan load on a small server, and remove the extended protection setup cleanly before uninstalling.
1. Wordfence Security
Verdict: The most complete all-in-one security plugin that runs inside WordPress, but it uses your own server resources, does nothing against floods that reach your server, and needs tuning on weak hosting.
What it is
Wordfence Security is made by the company that now trades as Wordfence and is one of the best-known names in WordPress security. It is a single plugin that bundles an endpoint web application firewall, a malware and file scanner, login security with two-factor authentication, login attempt limits and a live view of traffic. It has a free version that is genuinely useful and paid tiers above it.
The company also runs its own vulnerability research and publishes a vulnerability database, which feeds the firewall rules and the scanner. That research arm is a real part of the product: the rules you get are written by people who track WordPress plugin flaws as their main job.
For a reader deciding between products, the useful way to see Wordfence is as the closest thing to a one-plugin answer to several layers at once. It covers the firewall layer, the malware scanning layer, the login hardening layer and part of the vulnerability layer. It does not provide an activity log in the audit-trail sense, it does not make backups, and it cannot act before traffic reaches your server. Those gaps are the ones to fill around it.
How it works
The firewall is PHP code that runs on your own server. In its basic mode it loads as part of WordPress, which means any code that runs earlier than the plugin is not covered. In its extended protection mode it is loaded through a PHP setting, the auto prepend file directive, so it runs before WordPress itself starts. Extended protection is the setup worth aiming for, but how it is configured depends on your server software, and some hosts restrict it.
When a request arrives, the firewall compares it with rules for known exploits and general attack patterns, checks rate limits and blocked addresses, and either lets it through or returns a block page. Because it runs inside your PHP environment it can use context such as whether the visitor is logged in. The price is that every uncached request pays a small processing cost, and cached pages served directly by your web server or CDN never reach it at all.
The scanner reads files on your server. It compares core, plugin and theme files against the originals published in the official directory where those exist, looks for known malicious patterns, checks posts and options for suspicious content and URLs, and reports outdated, abandoned or known-vulnerable software. Premium tiers receive new rules and signatures in real time, while the free version receives them after a delay; confirm the current arrangement on the vendor page.
Login security adds two-factor authentication using an authenticator app, limits on failed logins and an option to add a CAPTCHA to login. A separate central dashboard, Wordfence Central, lets you view several sites at once.
Strengths
- The firewall sees requests in context from inside WordPress and can load before WordPress starts in extended protection mode.
- The free version includes a firewall, scanner and two-factor login, so a site on a zero budget still gets several layers.
- The scanner compares core, plugin and theme files against known originals, which is the most precise way to spot a tampered file.
- Vulnerability research is done in-house, so rule updates and advisories come from people who work on WordPress flaws daily.
- A central dashboard shows several sites together, which helps small portfolios without extra tools.
Trade-offs
- It runs on your server, so scans and per-request filtering use your CPU and memory, which hurts most on small shared plans.
- It cannot stop traffic before it reaches your server, so it does little against floods and bandwidth abuse.
- Extended protection depends on server configuration and must be removed cleanly before you uninstall, or the site can fail to load.
- Fully cached pages skip PHP, so the firewall never inspects them.
- The free tier receives rule and signature updates later than paid tiers, which matters most in the days right after a new flaw is published.
- Scan results can be noisy on sites with custom or deliberately obfuscated code, so expect to review and mark findings.
Setup and traps
Install the plugin and walk through its setup steps, giving it an email address that a human reads. Set the firewall up in extended protection mode if your host allows it; the plugin shows the server type it detects and the steps involved. Some managed hosts need to apply the change for you, so ask support rather than editing server files blind.
Leave the firewall in its learning mode for a short period if you run forms, a store or an API, then switch it to enabled and protecting. Learning mode watches your normal traffic so the first live blocks are less likely to catch legitimate requests. Add your own IP address, your uptime monitor and your payment provider’s callback addresses to the allowlist where your plan permits.
Turn on two-factor authentication for every administrator and shop manager and save the recovery codes somewhere that is not the same password manager entry as the password. Schedule scans for a quiet hour. Then tidy the alert settings: choose the severity at which you want email, otherwise the first week will teach you to ignore the inbox.
The traps are predictable: leaving extended protection configured after deleting the plugin, running a second security plugin with its own firewall, and forgetting that page caching hides requests from the firewall.
Costs beyond the price tag
The free version costs nothing in licence fees but does cost server resources and your attention for tuning. The paid tiers renew annually per site, so a portfolio multiplies the cost, and letting a licence lapse quietly puts you back on delayed rule updates. If your host already filters traffic, you may be paying for a second layer that adds latency without adding coverage. Higher tiers that include help with cleanups and incidents are priced as services, so read what is and is not included before you assume you can hand over a hacked site.
Pick it if
Pick it if you manage one site or a few sites on a VPS or a decent shared host, you cannot or do not want to change your DNS, and you want a firewall, a scanner and two-factor login without assembling three tools. It also suits a developer who wants readable logs of what was blocked and why, and a site owner who wants the free tier now with the option to pay later.
Skip it if
Skip it if your host’s plan is tight on CPU and memory and already includes its own firewall, or if you already use a cloud firewall in front and prefer not to filter twice. Skip it as your only layer if you need protection against traffic floods, a managed cleanup done for you, or an audit trail of editorial and user changes. It is also a poor fit if nobody will read the alerts.
Compare with: Cloudflare WAF, Sucuri, Solid Security.
2. Patchstack
Verdict: The most focused answer to the layer behind most compromises, known vulnerabilities, but it does no malware scanning, login hardening or logging, so it sits beside other tools rather than replacing them.
What it is
Patchstack is a security company that concentrates on vulnerabilities in WordPress core, plugins and themes. It maintains a vulnerability database, publishes advisories and sells a service that watches the software installed on your site against that database. Its plugin connects your site to a web dashboard where you see what is vulnerable, what has been fixed and what is not yet patched.
The company works closely with plugin developers and security researchers, and it runs programmes through which researchers report flaws. That ecosystem is the real asset: the product is only as good as the speed and accuracy of the data behind it.
It is easy to mistake Patchstack for a general security plugin because it appears next to Wordfence and Solid Security in lists. It is not. It does not scan for malware, it does not protect the login page, it does not keep an audit log and it is not a general-purpose firewall. It does one thing: it tells you precisely when something you run is known to be dangerous, and in paid tiers it can block the exploitation of that specific flaw before you have updated.
That narrowness is the reason to consider it. The most common way in is a known flaw in installed software, and Patchstack addresses that layer directly.
How it works
The mechanism has two halves. The first is detection. The plugin reports the list of installed core, plugin and theme versions to the service, which compares it with the vulnerability database and raises an alert when a match appears. The value is in how fast new entries arrive and how precisely they identify the affected versions, so you are not chasing alerts about plugins you have already patched.
The second half is virtual patching. For a vulnerability in a plugin, the research team writes a mitigation rule that recognises the specific request pattern that triggers the flaw. The rule is delivered to the plugin on your site and checked when requests arrive. If a request matches, it is blocked, while the vulnerable plugin files stay exactly as they are. You get time to test an update on staging, or protection while waiting for a developer to ship a fix.
Two limits follow from this design. A virtual patch exists only for vulnerabilities that have been reported, triaged and turned into a rule, so it cannot defend against a flaw that nobody has disclosed. And a virtual patch is a stopgap, not a permanent fix: the aim is still to update, replace or remove the vulnerable plugin. For abandoned plugins that will never be patched, a virtual patch can reduce risk, but the safer move is to replace the plugin.
Because the product depends on a list of versions plus compact rules, it is light on the server compared with a full file scanner.
Strengths
- Alerts are specific to plugin and theme versions you actually run, so they are easy to act on.
- Virtual patching buys time when an update is not available yet or cannot be applied immediately.
- It has a very small footprint because it does not crawl your file system.
- The dashboard is suited to agencies who need one view across many client sites.
- It works alongside any firewall or scanner without competing with them.
Trade-offs
- It does not scan for malware, so a site that is already infected will not be told by this tool.
- It has no login hardening, two-factor authentication or activity logging.
- Virtual patching covers only reported vulnerabilities and does not stop unknown or zero-day flaws.
- Virtual patching and the broader feature set are in paid tiers, which are priced per site.
- Its usefulness depends on someone acting on alerts; an alert that nobody reads protects nothing.
- Flaws in your own custom code are outside its database.
Setup and traps
Create an account on the service, add your site and install the connector plugin when prompted. Check that the dashboard lists your core version, plugins and themes correctly, including premium and custom ones, since a missing plugin is a gap in coverage. Set the email address and, if you use it, the channel that receives alerts, and decide who owns responding to them.
If your plan includes virtual patching, enable it and confirm on the dashboard that it is active for each site. Run a first review: any plugin with a known unpatched vulnerability should be updated, replaced or removed that day, not left on the list. Staging helps here, so you can test the update before it goes live.
For agencies, group sites by client, set a consistent alert recipient and agree what response time each severity needs. The common traps are connecting a site and never reading the alerts, assuming the free tier gives blocking, and forgetting premium plugins that do not appear in public listings. Another trap is treating virtual patching as a reason to postpone updates for months. It is a bridge to a proper update, not a replacement for one.
Costs beyond the price tag
The monitoring is cheap or free, but virtual patching is a paid feature and pricing is per site or per bundle, so a large fleet is a real line item. You will also need a separate answer for the layers Patchstack does not cover: malware scanning, login protection, logging and backups. The biggest hidden cost is time. Responding to alerts means updating on staging, testing and deploying, which is work whether or not the tool is free.
Pick it if
Pick it if you run a WooCommerce store, a membership site or a fleet of client sites where an emergency update is risky and you want a stopgap plus clear alerts. Pick it if your host already provides a firewall and malware scanning but not vulnerability intelligence. It is also a good first addition for a site owner who updates monthly and wants to know about dangerous flaws in between.
Skip it if
Skip it as your only security tool: it will not tell you about malware, a stolen password or who changed what. Skip it if you want a free all-in-one plugin and are happy with the vulnerability data inside a suite such as Wordfence Security or Jetpack Protect. Also skip it for a tiny hobby site you check once a year, where the effort of acting on alerts is more than the site justifies.
Compare with: Jetpack Protect, Wordfence Security.
3. MalCare
Verdict: An easy, light scanner with one-click cleanup, but the analysis happens off your server, the cleanup is automated, and it does not tell you how the attacker got in.
What it is
MalCare is a malware security product from the team behind the BlogVault backup service. It is built around one problem: finding malware on a WordPress site and removing it without the owner having to read code. A small plugin runs on your site and talks to a cloud service that does the heavy analysis. A dashboard shows scan results and offers cleanup. Paid plans add automated cleanup, a firewall, login protection and bot protection.
The positioning is simplicity. Many security plugins present dozens of switches. MalCare presents a scan result and a next step.
That simplicity has a trade-off worth understanding. You hand off detection and cleanup to a vendor, which is great for a person who does not want to learn about obfuscated PHP, and less good for a developer who wants to know exactly why a file was flagged. It sits mainly on the malware scanning and cleanup layer, with some firewall and login features around it. It is not primarily a vulnerability intelligence product, and it is not an audit log. Think of it as the layer that answers “is something malicious on my site right now, and can you remove it”.
How it works
The plugin collects information about your site, such as file data and parts of the database, and sends it to MalCare’s servers. The analysis runs there, not on your host, which is why this design is described as light on the server. When a scan finishes, the dashboard reports what it found. Detection is described as combining known signatures with analysis of how code behaves, and the vendor has the advantage of seeing many sites, but the details of the detection logic are not something you can inspect.
Cleanup in paid plans is automated: the service removes the malicious code it identified from files and database entries, so you do not manually edit infected files. That is convenient, and it is also the part to treat carefully. Automated cleanup edits live files. Take your own backup first, even if the tool offers its own restore point, and review the site afterwards. A tool that reliably removes what it detects still does not know about a backdoor it failed to detect.
The firewall and login protection layers in paid tiers add basic filtering and bot defence in front of the dashboard. They are positioned as part of the same service rather than a configurable rule engine, so you get less control than with a dedicated firewall.
Because data about your site leaves your server for analysis, consider your privacy obligations if the site holds regulated or sensitive information, and read what the vendor says about what is transferred and stored.
Strengths
- Off-server analysis keeps the load on a small shared host low, which avoids scans that time out or slow the site.
- The interface is one of the simplest in the category, so a non-technical owner can understand what to do next.
- Automated cleanup in paid tiers removes the need to hand-edit infected files.
- The multi-site dashboard suits agencies and anyone managing several sites.
- It combines scanning with some login protection and bot defence in one service.
Trade-offs
- Detection logic is a black box, so you cannot easily audit why something was flagged or missed.
- Automated cleanup edits live files, so you need a recent backup of your own before you run it.
- Cleanup does not reveal how the attacker got in, so reinfection is possible unless you fix the cause.
- Site data is sent to the vendor for analysis, which may matter for regulated or confidential sites.
- The firewall and login features are less configurable than those in a dedicated suite.
- Scanning and cleanup depend on the vendor service being reachable.
Setup and traps
Install the plugin, connect it to a MalCare account and let the first scan run. Compare the result with what you expect: a clean site should come back clean, and a site you know was recently compromised should show findings. If you are on a free plan, you can see what is flagged but cleanup needs a paid plan.
Before running any automated cleanup, take your own full backup of files and database and store it off the server. If you have a staging site, run the cleanup there first, check the pages that matter, and only then repeat it on production. After the cleanup, change administrator passwords, check for unknown administrator accounts and review installed plugins against what you expect.
If you turn on the firewall and login features, test the login page, the checkout and any contact forms straight away. Add your own address and any monitoring service to the allowlist if the plan allows it.
The usual traps are treating a clean scan as proof of safety, skipping the backup because the vendor offers a restore point, and not asking why the infection happened. A reliable cleanup of an unpatched plugin flaw is a temporary fix.
Costs beyond the price tag
Free scanning is useful, but cleanup is where the paid plans start, so the most important feature is not free. Plans are per site or per bundle, which affects agencies with many small sites. If you already pay for backups with the same company or another provider, you may end up with overlapping backup features. The real cost of an automated tool is the follow-up: investigating the entry point, updating the vulnerable software and rotating credentials still falls to you.
Pick it if
Pick it if you are not technical and want one tool that scans and can clean, if your hosting is modest and heavy on-server scanners cause problems, or if you manage several client sites and want a single dashboard with plain-language results. It is a sensible choice for a brochure site or small shop where the main fear is waking up to an infection.
Skip it if
Skip it if you want full control over detection and want to see why each file is flagged, or if your site holds data that should not leave the server for analysis. Skip it as a stand-alone defence: it does not replace vulnerability alerts, an audit trail or tested backups. If you need a human team to investigate and clean a serious compromise, a managed cleanup service such as the one Sucuri sells may fit better.
Compare with: Wordfence Security, Sucuri.
Still undecided after 3 profiles?
Take the 60-second quiz4. Solid Security
Verdict: The strongest login and site-hardening toolkit in this list, with file change detection on top, but it is not a firewall in the Wordfence or Sucuri sense and it will not clean a hacked site.
What it is
Solid Security is the current name of the plugin long known as iThemes Security. It is made by SolidWP, the company that took over the iThemes security and backup products, so older tutorials, forum threads and videos that mention iThemes Security describe the same product line. It has a free edition, called Basic, and a paid Pro edition.
Where the suite differs from Wordfence or Sucuri is the centre of gravity. It is built around the idea that most WordPress breaches go through the front door, so it concentrates on login protection, user account controls, and a long list of hardening changes that remove easy targets. It also adds file change detection and some version management. It reads more like a checklist you work through than an engine that sits in front of your server.
That framing is useful when you decide what else you need. Solid Security gives you strong answers on login hardening and part of the hardening and file integrity layers. It does not give you a deep exploit firewall with a research team writing rules, a cloud malware cleanup service or a full audit-trail product. It is a good base layer rather than a complete stack.
How it works
Solid Security is a collection of modules, each of which changes how WordPress behaves. The brute force modules count failed logins per account and per IP address and lock out repeat offenders. Two-factor authentication can be required for chosen roles, and the plugin can enforce stronger password rules. Hardening modules switch off or restrict things attackers like, for example the built-in file editor and parts of XML-RPC, and tighten defaults that WordPress leaves open. Some of these changes work by writing rules to server configuration files, and how well that works depends on whether you run Apache, LiteSpeed or nginx, so check what the plugin can and cannot apply on your server.
File change detection builds a record of files on disk and then reports files that were added, changed or removed, which can reveal tampering that happens outside WordPress. The signal is only as useful as your tuning: on an active site with automatic updates, legitimate changes are constant, so the plugin lets you exclude directories such as caches and uploads.
It also performs checks that compare your installed software with known vulnerability data from a third-party source and can help keep software current. Treat the vulnerability layer here as a useful awareness feature and check on the vendor page how it works and which edition it belongs to.
Because most of the work happens at login time, in settings changes and in scheduled checks, the overhead on normal page views is small compared with a request-filtering firewall.
Strengths
- It offers the widest set of login protections in this list: failed-attempt limits, enforced two-factor authentication by role and stronger password rules.
- The hardening checklist lets a non-expert remove common weak points one at a time.
- File change detection spots files added or edited outside the normal update flow.
- The overhead on ordinary page views is low because it does not inspect every request like a heavy firewall.
- The same maker has long experience with WordPress management and backups, so the plugin is mature.
Trade-offs
- It is not a deep exploit firewall, so it does little against a plugin flaw that bypasses the login screen.
- It does not provide signature-based malware scanning or cleanup of an already infected site.
- Some hardening modules write server rules and can cause lockouts or conflicts if you flip them without reading the explanation.
- File change reports are noisy on sites that update automatically unless you tune the exclusions.
- The best features sit in the paid Pro edition, so the free version covers less than the marketing might imply.
- Because the product has been renamed, older guides contain outdated menu names and settings.
Setup and traps
Install the plugin and run its setup guidance. Before you enable anything that locks users out, take a backup and make sure you have a second route into the site, such as hosting file access or a second administrator account. The most common support problem with login-hardening plugins is the owner who enables two-factor, loses the phone and has no recovery code.
Begin with the low-risk changes: enable two-factor authentication for administrators and anyone who can publish or manage orders, require strong passwords, and turn on login attempt limits. Allow yourself a few trial logins to confirm that the lockout sends the notice to an email address you can read. Then work through the hardening modules one at a time, loading the front end and the admin after each change.
Set up file change detection last, and add exclusions for cache and upload folders on day one so the first email is not a thousand lines of noise. Finally, decide how this plugin sits beside the other layers. If you use Wordfence, Solid Security’s login features will overlap with its login security, so choose one owner for two-factor and login limits. If you use a cloud firewall, check that IP-based lockouts see real visitor addresses and not the proxy’s.
Costs beyond the price tag
The free edition is useful, but several of the features people buy it for, such as extended user controls and some of the stronger login options, sit in the paid edition and renew annually. Multi-site pricing scales with the number of sites. The main hidden cost is configuration time and the risk of self-inflicted lockouts, so allow an hour to read what each setting does. You will still need separate answers for firewalling, malware cleanup, activity logging and backups, so factor those in before you describe the site as protected.
Pick it if
Pick it for a membership site, a store with several staff accounts, or a site run by a team where passwords, roles and dashboard access are the main exposure. Pick it if you like checklists, want strong two-factor and login controls and plan to buy firewall and vulnerability layers separately, perhaps a DNS-level WAF and a vulnerability service. It suits an owner who will sit down for an hour and configure it properly.
Skip it if
Skip it if you want a set-and-forget all-in-one with a strong request firewall and malware scanner, in which case Wordfence Security or a cloud firewall fits better. Skip it if you already have two-factor and login limits provided by another plugin or by your host, because duplicate login protections cause confusing lockouts. Do not buy it expecting it to clean up an infection.
Compare with: Wordfence Security, WP Activity Log.
5. Sucuri
Verdict: A strong pairing of a cloud firewall with a managed cleanup service, but the firewall needs DNS changes and a locked-down origin, and the free plugin alone is a monitor rather than protection.
What it is
Sucuri is a security company that is part of GoDaddy. It is best known for website security and malware cleanup, and its offer has two quite different halves that people often confuse. The first is the free Sucuri Security plugin for WordPress. The second is the paid platform: a cloud website firewall that sits in front of your site, plus a cleanup and monitoring service run by Sucuri’s staff.
The plugin is mostly an observer. It runs integrity checks of core files, keeps an audit trail of events inside WordPress, runs remote scans of your public pages for visible malware, checks whether the site appears on security blocklists, applies some hardening and sends alerts. It does not firewall requests on its own.
The platform is the part that changes your security posture. Traffic is routed through Sucuri before it reaches your server, so malicious requests can be stopped at the edge, static content can be cached and the origin sees less load. If a compromise happens, the service includes people who investigate and clean it, and who can help get a site removed from blocklists.
This split matters when you read reviews, because people who tried only the free plugin and people who used the full platform are describing different products.
How it works
With the firewall, you change DNS so that your domain resolves to Sucuri’s network instead of directly to your server, usually by pointing the address record at the vendor or by changing nameserver settings as their instructions describe. Visitors reach Sucuri first, which inspects each request, blocks what matches attack rules, serves cacheable content from its own network and forwards the rest to your origin. It also terminates the connection for visitors, so you will need to understand how your certificate is handled at the edge.
The step that is easy to miss is locking down the origin. If your server still answers requests that arrive directly at its own IP address, an attacker who finds that address can skip the firewall completely. The standard fix is to allow connections only from the vendor’s address ranges and refuse the rest. Do it at the host firewall or the web server if you can.
The plugin has a different mechanism. Its remote scanner fetches your public pages and looks for injected scripts, spam links and similar visible malware, so it cannot see a backdoor that only runs on the server and never shows in a page. Its file integrity checks compare core files with the originals. Its audit log records events, and since a log stored only on a compromised server can be altered, check where the plugin keeps it and how long it is retained.
The cleanup service is human-led, so it can investigate and address infections that an automated tool cannot, subject to the plan you buy.
Strengths
- The cloud firewall filters traffic before it reaches your server, which helps against floods and keeps bad requests off your PHP workers.
- Cleanup is done by people, which suits a serious or repeated infection better than a button.
- Blocklist monitoring and help with removal address the reputation damage that follows an infection.
- The free plugin adds integrity checks, an audit trail and alerts to any site at no licence cost.
- Edge caching can reduce load on the origin, which helps small servers.
- It puts firewall, cleanup and monitoring with one vendor, which simplifies who to call.
Trade-offs
- The firewall requires DNS changes and careful handling of certificates, which is a barrier for non-technical owners.
- An unlocked origin lets attackers bypass the firewall entirely, and this is the most common setup mistake.
- The free plugin does not block anything, so it is not protection on its own.
- The remote scanner cannot see server-only malware that does not appear in public pages.
- Aggressive rules and caching can interfere with carts, checkouts and logged-in pages until exclusions are set.
- The plans are priced per site, which adds up for agencies with many small sites.
Setup and traps
Start with the free plugin: install it, register it and review the integrity and audit settings. Decide where alerts go. Then decide whether the platform is worth adding. If it is, plan the DNS change for a quiet period. Before changing anything, lower the TTL on your DNS records so a rollback is quick, record the current records and confirm you know how to restore them.
After the firewall is active, check that the site loads, that the certificate works end to end and that the real visitor IP address is passed to WordPress so that logging and login limits see actual visitors and not the proxy. If you run WooCommerce or a membership area, make sure that cart, checkout, account and admin pages are excluded from caching and that payment callbacks and API clients are not blocked by rules.
Then lock down the origin so it accepts web traffic only from the vendor. Test by requesting the site directly by the server’s address and confirm it refuses. Finally, check the logs after a week to see what was blocked, and tune the false positives.
The traps are leaving the origin open, forgetting the certificate on the origin, caching logged-in pages and treating the plugin as if it were the firewall.
Costs beyond the price tag
The firewall and cleanup are subscriptions per site, and plans differ in what they include, so read exactly how many cleanups and which firewall features you are paying for. Moving DNS into a vendor’s network adds a dependency: if you leave later, you must unwind it carefully. Edge caching has a learning curve and a purge workflow. If your host already offers a firewall or CDN, you may be paying for two filtering layers. Budget the time to configure exclusions and review blocks, and the cost of locking down the origin properly.
Pick it if
Pick it if you want a cloud firewall and a human cleanup service from one vendor, your site is a store, a lead-generation site or a client site where an infection is costly, and you can change DNS. Pick it if you have been hacked before and want someone else to own detection and recovery. The free plugin on its own also suits any site that wants file integrity checks and an audit trail without a licence.
Skip it if
Skip the platform if you cannot or will not touch DNS, if you already run a cloud firewall such as Cloudflare in front of the site, or if you run many tiny sites where per-site pricing makes no sense. Skip the free plugin as your only defence: it monitors but does not block. If your main problem is vulnerable plugins rather than active attacks, a vulnerability service gives more value for the money.
Compare with: Cloudflare WAF, MalCare, Wordfence Security.
6. WP Activity Log
Verdict: The best dedicated audit trail, and invaluable when something goes wrong, but it blocks nothing, writes to your database and tells you only what happened inside WordPress.
What it is
WP Activity Log is an audit trail plugin made by Melapress, which used to trade as WP White Security. It records what happens inside a WordPress site: who logged in, who created or deleted a user, who changed a role, who installed or activated a plugin, which post was edited, which setting was changed and from which IP address. It has a free version and a paid Premium version.
It is not a firewall, a scanner or a vulnerability tool, and it is worth being clear about that, because a list of security plugins can make it look like a rival to the others. It is not. It is the layer that tells you what happened. Without it, after a compromise you are guessing: was that new administrator created by your freelancer or by an attacker, and when did the change happen?
The product also has a second life outside security. On a team site it settles disputes about who changed a page or a price. For an agency it is evidence of what was done on a client site and when. For a membership or compliance-minded business it is the record of changes that a policy may require. Those uses are real, and they are the reason some owners install it even on sites that are well protected.
How it works
WordPress emits events when things happen: a user logs in, a post is updated, an option changes, a plugin is activated. The plugin hooks into those events, builds a record from them with the user, role, IP address, time, object and details, and stores the record in its own tables in your site’s database. A viewer in the admin lets you search and filter by user, event type, date and IP address, and the paid version adds reporting, notifications by email or text message and coverage of events from other plugins, such as WooCommerce.
Two consequences matter for security. First, a log that lives only in the same database an attacker has taken over can be edited or erased, so for serious use you want to mirror it to an external database or a log service, which is one of the features usually offered in the paid tiers. Second, the plugin sees events that WordPress knows about. A backdoor file dropped directly onto the server, or a change made by editing files, does not pass through WordPress and will not appear in the log, which is why you pair it with file integrity checks.
Because each event is a database write, a busy site with detailed logging generates a lot of rows. The plugin offers retention settings and the choice of which event types to record, and you should set them deliberately so the table does not grow without limit and you do not delete the evidence you need.
Strengths
- It answers the first question of any incident, who did what and when, with filters that make the answer quick to find.
- Real-time alerts for a small number of critical events, such as a new administrator, give early warning of account compromise.
- It covers multi-user sites well: roles, logins, sessions and content changes are all attributable.
- Support for popular plugins in the paid edition extends the log to store orders, forms and SEO changes.
- It does not interfere with firewalls, scanners or caching, so it fits next to any other layer.
Trade-offs
- It prevents nothing, so it never replaces a firewall, a vulnerability layer or two-factor login.
- It only records events that pass through WordPress, so direct file changes and server-level access are invisible to it.
- Logging is database-heavy on busy sites unless you restrict event types and retention.
- A log stored in the same database can be altered by an attacker who controls the database, unless you mirror it elsewhere.
- Alerts, reports, external storage and wider plugin coverage are in paid tiers.
- Poorly tuned notifications will bury the few events that matter.
Setup and traps
Install the plugin and open its settings before it records everything by default. Decide which event types you need. For most sites that means logins and failed logins, user creation and role changes, plugin and theme installs and activations, settings changes and content changes. Exclude noisy events you will never read.
Set retention to a period that matches your needs. For incident investigation you want weeks or months of history, not days, so check how large the table gets after a week and plan the database accordingly. If your edition supports external storage, send the log to a separate database or service so an attacker cannot erase it from the same compromised site.
Next, configure notifications for the few events that deserve an interruption: a new administrator account, a role escalation, a plugin installed outside your normal maintenance window, or a login from an unexpected country. Route them to a person or a channel that is watched, and test it by creating a temporary user on a staging copy.
The traps are leaving logging at its broadest default, never reading the alerts, relying on the log in the same database for forensic evidence and expecting it to notice file-level backdoors.
Costs beyond the price tag
The paid edition is licensed annually by number of sites, and the features most security teams care about, such as alerts and external storage, are the paid ones. The log itself costs database space and write operations, which on small shared hosting can become noticeable. There is also a people cost: a log nobody reads is worthless, so someone has to own checking it and tuning the alerts. If a plan includes several extensions for specific plugins, check that your plugins are covered before you count on them.
Pick it if
Pick it if more than one person can change your site, if you are an agency that needs a record of what was done on a client site, if you run a store or membership site where unexpected changes would be costly, or if you want to shorten the time it takes to understand an incident. It is also a sensible addition for any site that already has a firewall and scanner and lacks visibility.
Skip it if
Skip it if you want protection rather than visibility: it will not block anything. Skip it on a one-person brochure site where you are the only editor and nobody else logs in, unless you want the extra evidence. Skip it if your hosting cannot spare the extra database writes. And skip the idea that it covers file-level compromise, because you will still need file integrity checks and a malware scanner.
Compare with: Solid Security, Sucuri.
Still undecided after 6 profiles?
Take the 60-second quiz7. Cloudflare WAF
Verdict: The cleanest way to filter traffic before it touches WordPress and your server, but it cannot see inside WordPress, scan files or block a stolen password, and a leaked origin IP or a rigid rule can undo it.
What it is
Cloudflare is a network and security company whose reverse-proxy service sits between your visitors and your web server. Its web application firewall, usually shortened to WAF, is one of the features of that service. It is not a WordPress plugin. It is a layer you apply by changing how your domain resolves, so it works the same for WordPress, a static site and a custom app.
It is on this list because the most important decision in this category is whether your firewall lives inside WordPress or in front of it. Cloudflare is the best-known example of the second approach, and a number of other cloud firewalls, including the Sucuri firewall, work in a similar way. If you choose a DNS-level firewall, you do not also need an endpoint firewall plugin, and that is the point of the stacking advice on this page.
What the service offers depends on the plan. In general terms there are managed rule sets that block common attack patterns, custom rules you write yourself, rate limiting for sensitive URLs, bot-related controls, protection against traffic floods and a CAPTCHA alternative that can protect forms. The free level offers a basic set and higher levels offer more control. Check the current plan comparison, because the exact allocation of features changes and not every control is available on every tier.
The official Cloudflare plugin for WordPress exists, but it mainly handles caching and purging. The firewall itself is configured in the Cloudflare dashboard, not in WordPress.
How it works
When you add your domain, you point its nameservers to Cloudflare, or in a partial setup point specific records at it. From then on, DNS answers for proxied records return Cloudflare addresses instead of your server’s address. A visitor connects to a Cloudflare data centre near them. There, the request is checked against your rules. Obvious attacks, requests from blocked countries or addresses, and traffic over your rate limits are blocked or challenged with a verification step. Clean requests are forwarded to your origin server, or served from cache.
The central point is that bad requests are stopped before they use your PHP, database or bandwidth. That is the property an endpoint plugin cannot offer. It is also why DNS-level firewalls are the main defence against floods of traffic.
The limits follow from the position. The edge cannot see whether a visitor is logged in to WordPress, cannot read your files, and cannot tell a stolen password from a legitimate login. It also forwards requests from other tools, so your origin must refuse any traffic that does not come through Cloudflare, otherwise an attacker who learns your server’s real address can connect to it directly and skip every rule. Restrict the origin to Cloudflare’s address ranges, and make sure that WordPress and your server see the real visitor address and not the proxy’s.
Take care with TLS settings: the encryption mode between Cloudflare and your origin should verify your certificate, because modes that do not can leave part of the journey unencrypted. And when you cache pages at the edge, exclude the admin, login, cart, checkout and account pages, and any API routes that carry personal data.
Strengths
- Attack traffic is stopped at the edge, so it never consumes your PHP workers, database or bandwidth.
- It is the strongest option here against floods and bot-driven load.
- Rules can protect specific URLs, such as the login page and XML-RPC, with rate limits or challenges, without any code on your server.
- One account can cover many domains, which suits agencies and anyone with a mixed estate of sites.
- A free level is available, so you can try the model before you pay for more rule sets.
- It does not depend on WordPress, so it keeps working even if a plugin is broken or disabled.
Trade-offs
- It cannot scan files, detect malware or tell whether a login is genuine.
- It requires DNS changes and a locked-down origin, and a mistake in either leaves you unprotected or offline.
- Rules that are too strict can block payment callbacks, REST clients, mobile apps or your own admin without any visible error on the site.
- Caching rules need care on WooCommerce and membership sites, because caching a personalised page leaks or breaks it.
- The free level has fewer rule sets and controls than the paid levels.
- Your site now depends on a third-party network for availability and DNS.
Setup and traps
Before you start, take a record of every DNS record at your current provider, because the import is not always complete. Add the domain to the service, review the imported records, and decide which should be proxied. Web records for the site and www usually are. Mail records must not be proxied.
Lower your TTL ahead of the change if you can, then switch nameservers during a quiet period. Once traffic flows through, set the encryption mode so that the connection to your origin is verified with a valid certificate. Install a certificate on the origin if you do not have one, since a mode that skips verification is not a safe shortcut.
Next turn on the managed rules available on your plan in a logging or challenge mode first, watch what they flag for a few days, then enforce. Add targeted rules: rate-limit or challenge the login page, restrict XML-RPC if you do not need it, and consider a verification step for the admin area. Create skip rules for payment gateway callbacks and other legitimate machine traffic, using the sender’s published address ranges where they exist.
Then lock the origin so it accepts traffic only from Cloudflare, confirm that WordPress sees the real visitor address, and set caching exclusions. Test a purchase, a login and a form submission before you call it finished. The usual traps are an exposed origin IP, a lingering unproxied record that reveals the server address, and a rule that blocks your own payment provider.
Costs beyond the price tag
The free level costs no licence fee but covers less than higher levels, and moving up is a plan change that applies to the whole zone, not a per-feature purchase. Plan features such as advanced bot controls or extra rule sets can sit at higher tiers. There is an operational cost: someone has to own the dashboard, keep origin restrictions current, review blocks and handle DNS in future. If you ever leave, you must reverse the DNS change and review what your site relied on, from caching to redirects, so factor in an exit plan.
Pick it if
Pick it if you can change DNS and want attack traffic and bot load kept off your server, if you run a WooCommerce store or busy site where PHP capacity is scarce, or if you manage many domains and want one place to apply protections. It is also a good choice if you want to retire an endpoint firewall that slows a modest server, as long as you fill the layers a cloud WAF does not cover with other tools.
Skip it if
Skip it if you cannot touch DNS, if your host already puts you behind its own cloud firewall, or if you would be unable to maintain rules and origin restrictions. Skip it as a complete answer: you still need vulnerability intelligence, malware scanning, login hardening, an activity log and backups. If you do not want to learn another dashboard, an endpoint plugin such as Wordfence Security is easier to live with.
Compare with: Sucuri, Wordfence Security.
8. Jetpack Protect
Verdict: A light and simple starting layer for vulnerability awareness, but the free tier mostly informs rather than blocks, and it leaves login hardening, logging and recovery to other tools.
What it is
Jetpack Protect is a standalone security plugin from Automattic, the company behind WordPress.com and the larger Jetpack plugin. It is a narrower product than Jetpack itself. Its core job is to check your WordPress version, plugins and themes against a database of known vulnerabilities and show you what needs attention. Paid tiers add malware scanning and further security features on top.
It is the easiest product in this list to understand. You install it, connect it and read a list. There is no firewall to tune and no rule set to learn, which is exactly the appeal for a site owner who is worried but not technical, and for a small brochure site where a heavy suite is more machinery than the site justifies.
It is useful to know what it is for. The free tier is a vulnerability awareness tool. It tells you that a plugin you run has a known problem, so that you can update or replace it. That alone addresses the most common route into a WordPress site, which is why a modest tool that is actually read can protect more than a feature-rich suite that is not.
It also ties into the broader Jetpack family, which includes backup and other services. If you already use that ecosystem, Protect fits naturally. If you do not want a site connected to a WordPress.com account, that is a consideration, since the plugin relies on a connection to Automattic’s service.
How it works
The plugin collects the list of installed core, plugin and theme versions on your site and checks it against a vulnerability database maintained by Automattic. Matches appear in the WordPress admin with a description and, where one exists, a fixed version, so the action is clear: update, or remove if there is no fix. Because the check is a comparison of version lists, not a crawl of your files, it has a very small footprint on the server.
In the paid tiers, malware scanning checks your site files for malicious code and reports what it finds. The scanning runs on Automattic’s infrastructure, which keeps the load off your host, and some paid tiers include help or automated fixes for known threats. The details of which features belong to which tier change over time, so look at the current plan page rather than relying on a summary.
It is important to understand what the free level does not do. It does not block a malicious request, it does not lock the login page, it does not record who changed what and it does not back up your site. It reports. If you pair it with another layer that acts, such as a firewall in front of the site, then the report becomes useful in a larger picture: it tells you which plugins to update first, while the firewall reduces the risk in the meantime.
As with any vulnerability database, coverage depends on what has been reported and catalogued. A plugin with a flaw nobody has disclosed will look clean, and a premium plugin distributed outside the main directory may be covered less thoroughly. Treat a clean result as the absence of known problems, not proof of safety.
Strengths
- It is the simplest vulnerability checker in this list, with almost nothing to configure.
- The free tier gives real awareness of known flaws at no licence cost.
- It has a small server footprint because it compares version lists instead of scanning every file.
- It comes from a major vendor with a long history in the WordPress ecosystem.
- It can grow with the site, with paid tiers adding scanning and further protection.
Trade-offs
- The free tier only tells you about problems and does not block anything.
- It does not provide login hardening, two-factor authentication or an activity log.
- It relies on a connection to the vendor account, which some owners will not want.
- Coverage is limited to known vulnerabilities, so unreported flaws and some premium plugins may not be covered.
- Features move between free and paid tiers over time, so the plan you choose today may change in what it contains.
- It does not manage a multi-site portfolio as well as the dedicated fleet tools.
Setup and traps
Install the plugin and connect it to a WordPress.com account when it asks. Let the first scan finish and read the list. For each item, decide the action: update it, replace it or remove it. Treat anything flagged as vulnerable with no fixed version as a candidate for removal, not for waiting.
Check the notification settings so that new findings reach an inbox that a person reads. The tool is only as useful as the attention it gets, and a free report that nobody opens is not a security layer. Put a recurring reminder in a calendar to review it weekly if you are the only person responsible.
Then use the result to drive your update routine. Test updates on a staging copy if the site matters, and take a backup before you apply them. If you do not already have backups, add them now, because Protect does not provide them.
If you consider the paid scanning tier, compare it with alternatives on what you actually need. Decide whether you want an automated scan, a cleanup service or a firewall, and check that you are not buying overlapping features from your host. The traps are installing it and never reading it, assuming that a clean report means a safe site, and leaving the vulnerable plugin in place because the update feels risky.
Costs beyond the price tag
The free tier has no licence fee, but it is a feature that leads to a paid ladder. The step to malware scanning and other protections is a recurring subscription, and the plan structure within the wider Jetpack family can be confusing, so read what each plan includes before you buy. There is also the cost of the connection to a WordPress.com account, which some teams will want to review for privacy and account ownership, especially on client sites where the account should belong to the client.
Pick it if
Pick it if you are a non-technical owner of a brochure site, blog or small business site and want a zero-cost, low-friction way to know when something you run has a known flaw. It is also a reasonable first layer on a site that is already behind a host-level firewall. Choose it if you already use other Jetpack services and prefer one vendor.
Skip it if
Skip it if you run a store, membership site or fleet where you need virtual patching, deeper vulnerability data, fine control over rules or reporting across many sites. Skip it if you do not want your site connected to a vendor account. And skip the idea that it is a full security plugin: you still need login hardening, a firewall that blocks, an activity log and backups, supplied by other tools.
Compare with: Patchstack, Wordfence Security.
Common mistakes to avoid
Running two firewalls or two full security suites
It feels safer to install Wordfence Security and a second suite, or to put a cloud firewall in front of a site that also runs an endpoint firewall that rewrites server rules. In practice the layers contradict each other. Both try to lock out IP addresses, both write rules, both send alerts, and a legitimate visitor can be blocked by one while the other says everything is fine. Admin screens slow down. Pick one firewall, either in front of WordPress or inside it, and let other tools cover the layers it does not.
Treating a malware scanner as protection
A scanner reports damage that has already happened. A clean scan means that nothing it recognises is present today, not that nothing can get in tomorrow. Owners who buy a scanner and stop there still depend entirely on plugin updates, passwords and luck for prevention. Count scanning as detection and cleanup, and look for separate answers to prevention: a firewall, vulnerability alerts with virtual patching, and login hardening. Then confirm someone reads the scanner’s alerts, because an unread alert is a missing alert.
Skipping two-factor login because a firewall is installed
A firewall blocks malicious requests, but a login with a stolen but valid password is not malicious from its point of view. Credential reuse across sites is common, and attackers try leaked passwords at scale. Two-factor authentication for administrators, editors and shop managers is one of the highest-value, lowest-cost settings on the whole page. Use an authenticator app instead of relying on email codes alone, store the recovery codes safely, and make sure you have a second way into the site before you enforce it.
Cleaning up without finding the way in
Deleting the malware and restoring a backup makes the site look normal, but if the entry point was an outdated plugin, a stolen password or a backdoor you did not find, the attacker returns. Many repeat infections happen because the backup already contained the intrusion, or because a dormant backdoor file was restored along with everything else. Use logs and the activity trail to find what changed first, update or remove the vulnerable component, rotate every credential, and then monitor closely for a few weeks after the cleanup.
Leaving the origin server reachable behind a cloud firewall
A DNS-level firewall protects only the traffic that goes through it. If your server still answers requests sent straight to its own IP address, an attacker who finds that address, perhaps from old DNS records, a mail header or a subdomain that was never proxied, can skip every rule. After you put a cloud firewall in front of the site, restrict the origin so it accepts web traffic only from the vendor’s ranges, remove or proxy stray records, and test by requesting the site directly by IP.
Disabling a protection instead of fixing the false positive
When a firewall blocks a contact form or a security scan flags a custom plugin, the quick reaction is to switch the feature off. That trades a visible problem for an invisible one. Find the rule or finding that fired, read the block log, and add a narrow exception for that specific URL, parameter or file. A learning or monitoring mode helps on a new install. A blanket exemption for a whole directory or a whole IP range gives an attacker the same exemption.
Keeping abandoned or pirated plugins and hoping the plugin covers them
No security plugin makes unmaintained or nulled software safe. An abandoned plugin with a known flaw will stay vulnerable forever, and a pirated premium plugin often contains the backdoor itself. A virtual patch or firewall rule can reduce exposure to a known flaw for a while, but the safe answer is to replace the plugin. Treat the vulnerability alerts as a prompt to remove what you do not need and to buy genuine licences for what you do.
Never testing the alerts or the restore
Most owners have never seen their own security setup block anything or send a real alert. The email goes to a retired address, the notification is filtered to spam, the backup restores only partially, or the activity log was never switched on for the event that mattered. A setup that has never been tested is a belief, not a control. Trigger harmless test events on a staging copy, confirm the message arrives where a person will read it, and practise a restore so the first time is not during an incident.
How to switch safely
Switching security tools is riskier than switching most plugins, because these products change how requests are handled, how logins work and what is written to server configuration files. A careless swap can lock you out, leave a firewall half removed or leave you unprotected for a few days. Do it in a deliberate order.
- Take a full backup and a second way in. Back up files and database off the server, and confirm you have hosting file access and a second administrator account. If you use two-factor, keep the recovery codes where you can reach them.
- Write down what the old tool does. Note its firewall exceptions, allowlisted addresses, country blocks, login limits, notification recipients and scan schedule. These settings are the institutional memory of the site and they vanish when you uninstall.
- Do it on staging first if the site matters. A store or membership site should see the new tool run against a copy before it touches production.
- Never run two firewalls at once. Disable the old one properly before enabling the new one. For an endpoint firewall that loads before WordPress, use the vendor’s own removal path so the server configuration it wrote is cleaned up. Deleting the plugin folder by hand can leave a directive that points at a file that no longer exists, which can take the site down.
- Replace the layer, then verify. Enable the new tool in a logging or learning mode if it offers one, and confirm it sees real visitor IP addresses. Re-create your exceptions, especially for payment callbacks, uptime monitors and any API clients.
- Check leftovers. Look at
.htaccess, the server configuration,wp-config.php, scheduled tasks and the database for settings the old tool left behind. Some leave tables behind, and a stale log table can grow quietly. - Re-test the whole stack. Run the checks in the next section: a failed login limit, a two-factor login, a test alert, a harmless blocked request, and a checkout and a form submission.
Special cases deserve extra care. Moving from an endpoint firewall to a DNS-level one means adding the new layer first, confirming it works, locking the origin and only then retiring the plugin firewall, so you are never unprotected. Moving from one malware scanner to another is low risk, but do not delete the old scanner’s history until you have compared the first scans, since a disagreement is a reason to investigate, not to ignore. Moving from one login protection to another is where lockouts happen, so keep the old two-factor active until the new one is confirmed on every privileged account.
For rollback, keep the old plugin’s files and your recorded settings available for a few weeks, keep the backup, and if the site misbehaves, disable the new tool first, then reinstate the old one. If the site is unreachable, rename the plugin folder over SFTP or your host’s file manager to deactivate it, then check the server configuration for leftover directives.
Test the shortlist on your own site
Security tools are the one category where you cannot judge by how the site looks. The setup either blocks and alerts or it does not, and the only way to find out is to try. Do the checks below on your own site, preferably on a staging copy, in this order, and never run them against a site you do not own or have permission to test.
- Map your layers. Write a short table with the seven layers from this page: firewall, vulnerability intelligence, malware scanning, login hardening, file integrity, activity logging and backups. For each, name the tool or host feature that owns it. Every empty row is a gap, and every row with two owners is a conflict to resolve.
- Prove the alert path. Create a temporary administrator account and watch for the notice. Edit a theme file by adding a harmless comment and see whether file change detection reports it. Install and deactivate a small plugin and check the activity log. If an expected alert does not arrive within the time you expect, the notification address, spam filter or settings are wrong.
- Test login protection. Try several wrong passwords from a browser you control and confirm the lockout happens and that you receive notice. Log in with and without a second factor on a privileged account, and test the recovery path with a spare account.
- Test the firewall on your own URLs. Add a harmless but obviously suspicious query string to a page on your own site, such as a fake script tag or a common attack pattern in a parameter, and compare the response with a clean request. A block page or a challenge is the sign you want, and the block log should show which rule fired. Also test the login page and XML-RPC against the rate limits you set. Whatever you see tells you what the rule set covers, which is information even when it is not a block.
- Test for bypass. If you use a cloud firewall, request the site directly by the server address and confirm that the origin refuses. If you use an endpoint firewall, request a page that your cache serves and remember that the firewall may not see it.
- Replay your real flows. Place a test order, submit your forms, upload a file, call your REST endpoints and run a webhook from your payment provider’s test mode. Look at the firewall log for blocks. False positives hide here.
- Measure the cost. Compare uncached response time, admin screen speed and the time a scan takes, before and after, using the same page and the same moment of the day, and watch the PHP error log and your host’s resource graphs during a scan. A scan that exhausts resources will show as slow pages or killed processes.
- Prove the restore. Restore your latest backup to a staging site and open it. Time it and write the steps down. This is your recovery plan.
- Run a fire drill. Using the incident order from the criteria section, rehearse contain, preserve, find the entry point, clean, rotate and monitor on staging so the first real run is not improvised.
After a week, review the blocks, alerts and scan reports. Too many alerts means you will start ignoring them, so tighten the settings. No alerts at all is not proof of safety: it may mean the notifications are not arriving. Repeat the tests after any major change such as moving hosts, changing DNS or switching a tool.
Glossary
- WAF
- A web application firewall, which inspects HTTP requests and blocks those that match attack rules before the application processes them.
- Endpoint firewall
- A firewall that runs on your own server inside or alongside WordPress, so it sees requests that reach your PHP but cannot stop traffic before it arrives.
- DNS-level firewall
- A cloud service that sits in front of your site, so visitors resolve to the vendor first and bad requests are blocked before they reach your server.
- Origin server
- The actual server that hosts your site behind a proxy or CDN. It should accept web traffic only from the proxy, or the firewall can be bypassed.
- Virtual patching
- A firewall rule that blocks the exploitation of a specific known vulnerability without modifying the vulnerable plugin or theme.
- Vulnerability
- A flaw in software that an attacker can use to do something they should not be able to, such as upload files or read data.
- Zero-day
- A vulnerability that is exploited before it has been publicly reported or fixed, so no patch or database entry exists yet.
- File integrity monitoring
- Checking files against a known good state or a previous snapshot to detect additions, changes or deletions.
- Brute force attack
- An attack that tries many passwords against a login, often automatically, in the hope that one works.
- Credential stuffing
- Trying username and password pairs leaked from other breaches, which succeeds when people reuse passwords across sites.
- Two-factor authentication
- A login that requires a second proof besides the password, such as a code from an authenticator app or a hardware key.
- Backdoor
- Hidden code that lets an attacker get back in after a cleanup, often disguised as a normal file or a fake plugin.
- False positive
- A legitimate request or file that a security tool wrongly blocks or flags as malicious.
- Audit log
- A record of events inside a system, such as logins, setting changes and content edits, kept so you can see who did what and when.
Read this next
How this list is made. Selections and fit ratings are editorial judgments from vendor documentation, public changelogs and how each product is typically used. WPresident has not benchmarked these products for this list, and no vendor paid for placement. Verify pricing, limits and compatibility on the vendor’s own site before you buy. Updated November 2026. See how we score and our editorial policy.
Frequently asked questions
Do I need more than one security plugin?
Usually you need more than one tool, but not more than one of each kind. A common stack is one firewall (an endpoint plugin or a cloud WAF), one vulnerability layer, a login hardening tool if the firewall does not cover it, an activity log, and backups. A single suite such as Wordfence Security can cover several of those at once. The mistake is adding a second tool that does the same job as the first, because they conflict.
Can I run Wordfence and Sucuri, or two firewalls, together?
Avoid running two firewalls that both filter requests and manage lockouts. Using the free Sucuri Security plugin for its audit log and integrity checks next to another firewall is a different matter, because it does not firewall requests. Using a cloud firewall in front with an endpoint plugin behind it can work if you decide which one owns blocking, but the safer default is one owner, with the other tools limited to scanning or logging.
Is a free security plugin enough?
For a small, low-risk site with good habits, a free tier can cover a lot: a free plugin may bring a firewall, scanner and two-factor login, and a free vulnerability checker adds awareness. What free tiers tend to lack is speed of updates, virtual patching, managed cleanup and detailed alerts. Judge by what the site would cost you if it went down for a week, then check on each vendor page what the free level includes.
Do I need a security plugin if my host has a firewall?
A host firewall covers some layers, not all of them. It typically blocks common attack patterns and may scan for malware. It rarely tells you which plugin on your site is vulnerable, enforces two-factor login on your admins or keeps an audit trail of changes. Ask the host in writing what is blocked, what is scanned and what is your responsibility, then buy only the layers that remain uncovered.
What is virtual patching and does it replace updating?
Virtual patching is a firewall rule written for a specific known flaw. It recognises the request that exploits the flaw and blocks it, so the vulnerable plugin is protected without changing its files. It does not replace updating. It buys time when no fix exists yet or when you need to test an update first. It only covers vulnerabilities that have been reported and turned into a rule, so unknown flaws remain.
Endpoint firewall or DNS-level firewall: which should I choose?
An endpoint plugin runs inside WordPress, knows about logged-in users and needs no DNS change, but uses your server resources and cannot stop floods. A DNS-level firewall filters traffic before it reaches your server, handles bot load well and offloads work, but needs DNS changes, a locked-down origin and careful exceptions. If you can change DNS and your site is busy, lean to the cloud option. If you cannot, use an endpoint plugin.
Will security plugins slow my site?
They can. An endpoint firewall adds processing to uncached requests. A file scanner reads many files and can strain a small hosting plan while it runs. An activity log adds database writes. A cloud firewall adds a network hop but often removes load from your server. The effect depends on your host and settings, so measure uncached page speed and admin speed before and after, and schedule scans for quiet hours.
What should I do first if my site is hacked?
Contain it first: take the site offline or into maintenance mode and change hosting and admin passwords. Then preserve evidence by copying the files, the database and the server logs before changing anything. Find the entry point using logs and file dates, clean or restore from a copy that predates the intrusion, reinstall software from clean sources, rotate every credential and key, patch the hole, and then monitor closely. Skipping the entry point step invites reinfection.
Does changing the login URL make my site secure?
It reduces noise from bots that hit the default login address, which keeps logs cleaner and can reduce load. It does not stop an attacker who has valid credentials or who finds the new address, so treat it as a minor convenience rather than a control. Spend the effort on two-factor authentication, failed-attempt limits and strong, unique passwords, which address the real risk.
Do I need two-factor authentication on every account?
Require it on every account that can change the site or touch money: administrators, editors, shop managers and anyone with access to settings, plugins or orders. For customers or members, offer it as an option unless the data you hold justifies requiring it, and be ready to support people who lose their device. Use authenticator apps where you can, and keep recovery codes safe.
Why does my security tool keep flagging a file I know is fine?
Scanners flag code that looks like what malware does, such as obfuscated strings or code that decodes and runs content. Legitimate premium plugins and custom code sometimes do the same, and modified core or plugin files are flagged by integrity checks. Compare the file with the original, ask the plugin author, and then mark the specific file as safe. Do not exclude whole folders, since that also hides real malware.
Do backups count as security?
Backups are recovery, not prevention, but they are part of any serious setup. A backup is only useful if it predates the intrusion, is stored off the server and has been restored at least once. A backup that contains a backdoor restores the problem. Keep several versions, test a restore to staging, and remember that restoring does not close the hole that let the attacker in.
How often should I scan my site?
Daily is a sensible default for most sites, scheduled for a quiet hour so that it does not compete with visitors. Heavier sites on weak hosting may need a lighter schedule or an off-server scanner. More important than the frequency is whether anyone reads the result. Alerts should go to a person, and a missed scan or a failing scan should itself trigger a notice.
Can a security plugin stop a DDoS attack?
Mostly no. A plugin runs on your server, so by the time it sees a flood of requests the traffic has already reached you. Rate limiting and blocking help against small abuse, but a real flood is handled at the network edge, either by a DNS-level firewall with traffic-flood protection or by your host. If this is a concern, choose a cloud firewall and ask your host what protection is included.



