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.
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.
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.
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
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.
A newline in the plugin settings let attackers write their own rules into .htaccess. The rule stops the settings requests that carry the injection.
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.
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
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
On top of the rules for each new vulnerability, the firewall blocks whole classes of attacks.
Most WordPress hacks start with a vulnerable plugin. We patch the ones being exploited, including abandoned plugins that will never get an update.
Bugs in PHP itself, like PHP2Shell, are blocked before they reach PHP, so old servers stay protected while you plan the upgrade.
SQL injection, cross-site scripting, remote code execution, file upload and path traversal attacks are blocked even without a specific rule.
Our team follows new vulnerabilities in WordPress, its plugins and themes, Joomla, Drupal, Magento and PHP, and the attacks we see across our network.
Each rule matches the exploit itself, so it stops the attack without breaking the feature for your real users.
The rule goes out to our whole network at once. There's nothing to install and no setting to change.
Apply the official fix on your own schedule. The virtual patch keeps protecting you in the meantime, and afterwards too.
Learn the basics: What is patching? · What is mitigation?
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