Virtual Patching

New vulnerabilities, patched on our network first

When a new vulnerability hits WordPress, a plugin, Joomla, Drupal or PHP itself, our team writes a firewall rule for it and pushes it to every site behind NOC. Your site is protected while you plan the real update, on your schedule.

Free 14-Day Trial
No credit card required. Included for every site.
Rules written by our security team, often within hours of disclosure
Applied to every site automatically. Nothing to install or update
Protects servers that can't be updated yet, even on end-of-life PHP

The gap between disclosure and update

Attackers start scanning for a new vulnerability soon after it goes public. Updating takes longer: you test the update, a plugin breaks, the developer is on vacation, or the server runs a PHP version that will never get a fix. That gap between disclosure and update is when most sites get hacked.

Instead of changing your code, the firewall recognizes the exploit on the wire and drops it before it reaches your server. You still update, but you no longer have to drop everything to do it.

We did this for PHP2Shell in October 2026: two remote code execution bugs in PHP itself, blocked for every PHP site behind the NOC firewall, including servers on PHP versions that will never be patched.

Virtual patches our team has written

A few of the vulnerabilities we have rules for, newest first. Every site behind the NOC firewall got each one automatically, with nothing to install or update.

PHP core
PHP2Shell (CVE-2026-109618, CVE-2026-109619) October 2026

Two unauthenticated remote code execution bugs in PHP itself, rated CVSS 9.2. Every PHP site behind the NOC firewall was patched at the edge, including servers on end-of-life PHP versions that will never get an official fix. Read more

WordPress core
wp2shell (CVE-2026-63030, CVE-2026-60137) July 2026

A pre-authentication code execution chain in WordPress 6.9 and 7.0 that goes through the REST API batch endpoint, fixed in 6.9.5 and 7.0.2. The edge blocks the batch endpoint in every form it can be requested.

CVE-2026-57623
W3 Total Cache: .htaccess injection June 2026

A newline in the plugin settings let attackers write their own rules into .htaccess. The rule stops the settings requests that carry the injection.

WordPress plugin
SureTriggers (OttoKit): admin account creation (CVE-2025-3102) April 2025

Versions up to 1.0.78 let attackers create administrator accounts through the plugin's REST API without logging in, on sites with no API key set. Those requests are refused at the edge.

Java
Log4Shell (CVE-2021-44228) December 2021

The Java logging bug that let one string run code on a server. The edge blocks the lookup strings in every request, including the encoded variants. Read more

WooCommerce
WooCommerce Store API: SQL injection (CVE-2021-32789) July 2021

An unauthenticated SQL injection in the WooCommerce Blocks Store API (the collection-data endpoint). The rule blocks the malformed values the exploit sends. Read more

What virtual patching covers

On top of the rules for each new vulnerability, the firewall blocks whole classes of attacks.

Plugins and themes

Most WordPress hacks start with a vulnerable plugin. We patch the ones being exploited, including abandoned plugins that will never get an update.

PHP and the server

Bugs in PHP itself, like PHP2Shell, are blocked before they reach PHP, so old servers stay protected while you plan the upgrade.

Every attack class

SQL injection, cross-site scripting, remote code execution, file upload and path traversal attacks are blocked even without a specific rule.

How it works

1
We track disclosures

Our team follows new vulnerabilities in WordPress, its plugins and themes, Joomla, Drupal, Magento and PHP, and the attacks we see across our network.

2
We write the rule

Each rule matches the exploit itself, so it stops the attack without breaking the feature for your real users.

3
Every site gets it

The rule goes out to our whole network at once. There's nothing to install and no setting to change.

4
You update when ready

Apply the official fix on your own schedule. The virtual patch keeps protecting you in the meantime, and afterwards too.

Frequently asked questions

Yes. A virtual patch blocks the known ways to exploit a bug, and buys you time to update properly. Keep updating WordPress, plugins, themes and PHP as usual, on your own schedule.

For vulnerabilities that are being exploited, often within hours of the details becoming public. Many attacks are also stopped before any specific rule exists, because they use techniques the firewall already blocks.

No. Virtual patching, and our managed rules in general, come with every site.

Yes. If you find a bug in your own application and need time to fix it, email support@noc.org and we'll write a rule for your site. See custom applications.

You can whitelist a URL or path from the dashboard right away, and our team will adjust the rule. Every block shows its rule ID, so you can tell us exactly what happened.

Learn the basics: What is patching? · What is mitigation?

Related features

Security that works, at a price that makes sense

$5per domain per month.

Get access to our full suite of services, including DNS, WAF/CDN and Monitoring, or use only what you need. Our WAF/CDN operates on a distributed anycast network with over 20 data centers, delivering exceptional global performance.

Free 14-Day Trial