Skip to content

Web application firewall for WordPress: where it actually runs

A host firewall watches packets. The requests that break plugins look normal on the wire and hostile to WordPress, so the rules belong inside the application.

Three interception layers before wp-config.php, the MU-phase and the main shield. A request that fails the rules never reaches a theme, a plugin or MySQL.

Web application firewall for WordPress

What the firewall checks

Method, path, query, body and the address that sent them. One decision, one line in the log.

Rules from the feed

Injection attempts in query strings, path traversal, bad HTTP methods, known scanner signatures and executable markup in bodies.

Three layers

Before wp-config.php, in the MU-plugin phase and in the main shield, so a failed request never reaches PHP work.

Reason in the log

Every block writes which rule fired and why. Tuning becomes reading, not guessing.

Plugin firewall and host firewall are different layers

A host firewall watches packets. It cannot see that a request is a POST to a vulnerable form field with a payload that only makes sense to one plugin. A plugin firewall sees exactly that, because it runs after TLS and before WordPress decides what to do.

The two do not replace each other. Keep the network perimeter with the host, put the application perimeter in the plugin, and let the log tell you which one acted.

Attempt limits and the ban ladder for the login form live in the same plugin: brute force protection.

Plugin firewall against host firewall

Setup order that avoids surprises

Five steps, and the third one saves the support ticket.

  1. Run the wizard

    It picks a protection level for the site and keeps risky options off.

  2. Allow your services

    Payment providers, uptime monitors, backups and your own REST calls cannot pass a browser check.

  3. Watch the log for a day

    The first day shows what normal traffic looks like before you tighten anything.

  4. Add rules for your paths

    The admin address and the API namespace are yours to restrict.

  5. Recheck after plugin updates

    A new version can add routes, and routes are what rules match.

Firewall rules setup steps

What the firewall does not do

It does not patch plugins

It stops the request that would exploit a hole. The plugin still needs an update.

It does not see dropped traffic

If the host already dropped a request, the plugin never receives it and has nothing to log.

Questions we hear

What site owners ask before turning the rules on.

Is the firewall free?
Yes. The WAF, the rule feed, the three interception layers and the log are in the free core. Paid plans add cloud checks, security headers, malware scanning and priority support.
Will it block Googlebot?
Real search engines pass. The plugin verifies crawlers by reverse DNS against the provider ranges, so a fake Googlebot is blocked while the real one is let through.
Does it work behind Cloudflare?
Yes. The plugin reads forwarding headers to find the real client address and blocks attempts to reach the origin directly. It also recognises challenges from external DDoS protection.
What happens during an attack?
Load drops instead of rising, because bad requests are rejected before PHP and the database start. Requests that pass the checks are served normally.
Do I need to edit server config?
No. Rules live in the plugin. The firewall export add-on writes Apache, nginx, fail2ban and iptables rules if you want the same blocks at server level.
Is a firewall WordPress plugin enough on its own?
For the application layer, yes. The plugin sees the request before WordPress loads and blocks it there. The network layer stays with your host or CDN, and the two do not conflict.
Do I need WAF rules for WordPress from Cloudflare or AWS?
Not for what the plugin covers. Its rules come from the threat feed and update with the plugin, so a CDN rule set is an extra layer rather than a replacement.

Put the firewall where the request is read

Install BotBlocker, run the wizard and read the log for a day. If a rule blocks a service you need, allow it by address or path.

Protected WordPress site