How virtual patching works

When a security researcher reports a hole in a WordPress plugin, the report says which request reaches the weak code: a parameter, an AJAX action, a REST route. A virtual patch is a rule that recognises that request and refuses it before the plugin’s code runs.

The rule sits in a firewall: either one in front of the server (a cloud WAF) or one that loads before WordPress on the site itself. The plugin stays as it is. Only the path an attacker would use is closed.

Why agencies use it

Fixes do not always arrive on time. A plugin can sit for days or weeks with a published hole and no new version, and some are abandoned for good. Updating is not possible until a fixed version exists, and switching the plugin off may break the client’s site.

A virtual patch covers that gap. It also covers sites where an update has to wait, for example because a new major version changes how the site works and needs testing first.

Its limits

  • It covers known holes only. A rule needs a published report to describe the attack.
  • It can miss other routes. If the weak code can be reached in a way the rule does not describe, the site is still exposed.
  • It is temporary. The fixed version is the real cure. Keep the rule only until the update is in.

How Keptstone handles it

On the Care + Protect + Speed plan, Keptstone’s firewall loads before WordPress on each site and carries patches for the holes found on the sites it looks after: a set of hand-written rules, not a vulnerability database. When a serious hole has no fix and no patch, Keptstone can close the plugin to visitors until a fix arrives. Each site’s page shows which holes are covered and how.

Questions

Is virtual patching the same as updating the plugin?

No. The vulnerable code is still on the site. The rule stops the known ways of reaching it. Update to the fixed version as soon as one exists, then the rule is no longer needed.

Does virtual patching slow a WordPress site down?

A rule runs before WordPress handles the request, so the cost is small, usually a few pattern checks per request. A page cache serves most visitors before any rule runs.

What if a hole has no fix and no virtual patch?

Then the safest choices are to switch the plugin off, replace it, or lock down the part of it that is exposed until a fix ships.