{"id":772,"date":"2026-11-14T10:44:13","date_gmt":"2026-11-14T05:14:13","guid":{"rendered":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/"},"modified":"2026-11-14T10:44:13","modified_gmt":"2026-11-14T05:14:13","slug":"wordpress-virtual-patching-explained","status":"publish","type":"post","link":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/","title":{"rendered":"Virtual Patching for WordPress: What Kinsta&#8217;s Patchstack Rollout Means, and What It Can&#8217;t Stop"},"content":{"rendered":"<p>On 12 November 2026, <a href=\"https:\/\/patchstack.com\/articles\/kinsta-now-protects-every-wordpress-site-it-hosts-with-patchstack\/\">Kinsta switched on &#8220;Vulnerability Protection, powered by Patchstack&#8221;<\/a> for every site it hosts. It&#8217;s included in every plan at no extra cost, and there&#8217;s nothing to install. In the first weeks, the two companies say it blocked more than 1.5 million exploitation attempts across more than 68,000 Kinsta sites. That&#8217;s a big number, and it&#8217;s a good moment to ask a plain question: what does virtual patching actually do for a WordPress site, and where does it run out?<\/p>\n<p>We did something a little different from the launch coverage. We took the four security incidents we wrote about in October and November 2026 and asked, for each one, whether virtual patching would have helped. The honest answer is: brilliantly for one, partly for one, and not much for two. That&#8217;s not a knock on the idea. It&#8217;s a description of what kind of layer it is.<\/p>\n<h2>What virtual patching is<\/h2>\n<p>A normal patch changes the vulnerable code. The plugin author fixes the bug, ships a new version, and you update. A virtual patch leaves the plugin&#8217;s code alone and instead blocks the specific requests that would exploit the bug. The hole is still there; the path to it is closed.<\/p>\n<p>Kinsta and Patchstack describe the process in three steps:<\/p>\n<ul>\n<li><strong>Identify.<\/strong> The system continuously compares each site&#8217;s plugins, themes and WordPress version against Patchstack&#8217;s vulnerability database.<\/li>\n<li><strong>Mitigate.<\/strong> When a match turns up, it applies a &#8220;RapidMitigate&#8221; rule to that site only, at the WordPress application layer.<\/li>\n<li><strong>Block.<\/strong> Requests that try to exploit the flaw are blocked, without any change to the plugin&#8217;s code. Once you update or delete the vulnerable plugin, the rule is removed automatically.<\/li>\n<\/ul>\n<p>Patchstack says it has more than 12,000 of these mitigation rules. Kinsta CEO Jon Penland put the pitch simply: &#8220;We identify which ones affect a customer&#8217;s site and apply protection automatically, so customers don&#8217;t have to chase them.&#8221; Patchstack CEO Oliver Sild: &#8220;Fast mitigation is non-negotiable for businesses of any size.&#8221;<\/p>\n<p>On Kinsta, this sits on top of what was already there: isolated containers, Cloudflare DDoS protection, an edge firewall, and the Bot Protection feature Kinsta added in June.<\/p>\n<h2>Virtual patching vs a generic WAF<\/h2>\n<p>These get lumped together, but they work differently.<\/p>\n<table>\n<thead>\n<tr>\n<th><\/th>\n<th>Generic WAF<\/th>\n<th>Virtual patching<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>What a rule targets<\/td>\n<td>Attack patterns, like SQL injection strings<\/td>\n<td>One specific known vulnerability in one specific plugin version<\/td>\n<\/tr>\n<tr>\n<td>Where it applies<\/td>\n<td>Broadly, to all traffic<\/td>\n<td>Only on sites where that vulnerable version is installed<\/td>\n<\/tr>\n<tr>\n<td>When it goes away<\/td>\n<td>It doesn&#8217;t; it&#8217;s always on<\/td>\n<td>When the plugin is updated or deleted<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A generic WAF is good at catching the obvious stuff. Virtual patching is aimed at the narrow, plugin-specific bugs that don&#8217;t look like a classic attack string at all, such as a request to an upload endpoint that simply forgot to check who&#8217;s calling it. You want both, and many sites have both.<\/p>\n<h2>Why this matters: the 2026 numbers<\/h2>\n<p>Patchstack&#8217;s <em>State of WordPress Security in 2026<\/em> report gives the case for it in four figures:<\/p>\n<ul>\n<li><strong>11,334<\/strong> new WordPress vulnerabilities in 2025, up 42%.<\/li>\n<li><strong>46%<\/strong> had no fix from the vendor at the time they were disclosed.<\/li>\n<li><strong>91%<\/strong> of vulnerabilities were in plugins.<\/li>\n<li>Heavily targeted flaws were mass-exploited in a median of <strong>5 hours<\/strong>.<\/li>\n<\/ul>\n<p>Read those together. Almost half the time there&#8217;s nothing to update to yet, and when a bug is popular with attackers, five hours is the median gap before mass exploitation. Nobody updates every site they look after inside five hours, and for the 46% there&#8217;s no update to install. That&#8217;s the gap virtual patching is built to fill.<\/p>\n<h2>The scorecard: four real incidents, October\u2013November 2026<\/h2>\n<p>Here&#8217;s how we think virtual patching would have fared against the incidents we covered in the last six weeks. This is our reading of how each attack worked, not a lab test.<\/p>\n<table>\n<thead>\n<tr>\n<th>Incident<\/th>\n<th>What kind of problem<\/th>\n<th>Would virtual patching help?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Bricksforge unauthenticated file upload (8 Oct)<\/td>\n<td>Classic plugin code flaw, exploited<\/td>\n<td><strong>Yes<\/strong>. This is the sweet spot<\/td>\n<\/tr>\n<tr>\n<td>WordPress core updater race, CVE-2026-119977 (CISA, 3 Nov)<\/td>\n<td>Core flaw with a window of seconds during updates<\/td>\n<td><strong>Partly<\/strong>. Rules helped; config and updating did the rest<\/td>\n<\/tr>\n<tr>\n<td>UpdraftCentral stolen keys (18\u201319 Oct)<\/td>\n<td>Genuine keys stolen; no code flaw, no CVE<\/td>\n<td><strong>Mostly no<\/strong>, until the feature was shut off<\/td>\n<\/tr>\n<tr>\n<td>PHP critical RCE (21 Oct)<\/td>\n<td>Bug in PHP itself, below WordPress<\/td>\n<td><strong>No<\/strong>. Needs a PHP update from the host<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>1. Bricksforge file upload: a clear win<\/h3>\n<p>On 8 October, Patchstack reported that an unauthenticated arbitrary file upload flaw in Bricksforge was being exploited. Unauthenticated means no login needed; arbitrary file upload means an attacker can drop their own file, often a PHP shell, onto your server. This is exactly the kind of bug virtual patching was made for: one plugin, one version range, one specific request to block. If your host matched the vulnerable version and applied a rule, the exploit request never reaches the plugin.<\/p>\n<h3>2. The core updater race: partial credit<\/h3>\n<p>CVE-2026-119977 is the WordPress core upgrader flaw that CISA added to its Known Exploited Vulnerabilities list on 3 November. It was fixed in WordPress 7.1.4. Wordfence saw attacks just 9 minutes after it deployed its own firewall rule on release day. The exploit window only lasts seconds, while an update is running. Firewall rules helped here, so virtual patching gets real credit. But the full fix also needed a configuration change (blocking access to <code>\/wp-content\/upgrade\/<\/code>) and actually updating WordPress. We covered the details in <a href=\"https:\/\/jnkplugins.com\/blog\/wordpress-core-upgrader-flaw-cisa\/\">our post on the core upgrader flaw<\/a>.<\/p>\n<h3>3. UpdraftCentral stolen keys: the wrong kind of problem<\/h3>\n<p>This one is the most instructive. On 18\u201319 October, attackers sent commands to sites using UpdraftCentral keys that had been stolen. The commands were signed with genuine keys. There was no bug in the plugin&#8217;s code to block, and there&#8217;s no CVE. A system that works by recognising known vulnerabilities in known versions can&#8217;t tell a stolen key from a real one, because from the site&#8217;s point of view, there&#8217;s no difference.<\/p>\n<p>Patchstack&#8217;s response was to block the UpdraftCentral command channel entirely. Dashboards showed affected sites as unreachable, while backups carried on. That&#8217;s a sensible emergency move, but it&#8217;s a blunt rule that switches a feature off, not a &#8220;patch&#8221; for a flaw. So we score it as mostly no, until the vendor or the feature itself was shut off. More in <a href=\"https:\/\/jnkplugins.com\/blog\/updraftcentral-keys-backdoor\/\">our write-up of the UpdraftCentral keys incident<\/a>.<\/p>\n<h3>4. PHP critical RCE: out of reach<\/h3>\n<p>On 21 October, Patchstack flagged attacks as ongoing against a critical remote code execution bug in PHP itself. That&#8217;s below WordPress. A rule running at the WordPress application layer can&#8217;t fix the PHP binary that runs it. The only real fix is your host updating PHP. We explained how to check your version in <a href=\"https:\/\/jnkplugins.com\/blog\/php-critical-security-release-wordpress\/\">our post on the PHP critical security release<\/a>.<\/p>\n<h3>What the scorecard tells us<\/h3>\n<p>One clean win out of four sounds weak, but that&#8217;s misleading. The win is in the biggest category by far: plugins are 91% of vulnerabilities, and virtual patching also covers the 46% that have no fix at disclosure. The misses were a stolen credential and a bug in the language runtime, which no WordPress-level rule was ever going to stop. Virtual patching is one layer. Updates, removing plugins you don&#8217;t use, keys with only the access they need, and working backups all still matter.<\/p>\n<h2>Which hosts include it<\/h2>\n<p>We&#8217;re only listing hosts where we&#8217;ve confirmed the details:<\/p>\n<ul>\n<li><strong>Kinsta<\/strong>: included in every plan at no extra cost, as of 12 November 2026.<\/li>\n<li><strong>Krystal<\/strong>: in its own words, <a href=\"https:\/\/krystal.io\/intelligent-wordpress-protection\">&#8220;Patchstack is included free with every Managed WordPress hosting plan. No paid upgrades or add-ons required.&#8221;<\/a><\/li>\n<li><strong><a href=\"https:\/\/jethost.com\/blog\/introducing-patchstack-wordpress-vulnerability-scanner\/\">JetHost<\/a><\/strong>: included on the Business plan; otherwise it&#8217;s a $3.99 per domain per month add-on.<\/li>\n<\/ul>\n<p>Other hosts may offer something similar. Ask.<\/p>\n<h2>Questions to ask your host<\/h2>\n<p>&#8220;We have a firewall&#8221; can mean a lot of things. These questions sort it out quickly:<\/p>\n<ul>\n<li>Is it per-vulnerability rules for specific plugin versions, or a generic WAF?<\/li>\n<li>Which vulnerability database does it use?<\/li>\n<li>Does it cover themes as well as plugins?<\/li>\n<li>What happens when a vulnerability has no vendor fix yet?<\/li>\n<li>Can I see a log of the attempts it blocked on my site?<\/li>\n<li>Does it cover sites on my plan, or only higher tiers?<\/li>\n<\/ul>\n<p>A host that does this properly will answer all six without needing to check.<\/p>\n<h2>If your host doesn&#8217;t offer it<\/h2>\n<p>You still have options:<\/p>\n<ul>\n<li><strong>Patchstack directly.<\/strong> Its <a href=\"https:\/\/patchstack.com\/pricing\/\">Developer plan is $69 a month, billed annually<\/a>, and includes &#8220;Rapid mitigation without changing code&#8221;. There&#8217;s a free tier too, but it gives you vulnerability alerts rather than patches, so check their current plans.<\/li>\n<li><strong>Wordfence.<\/strong> Wordfence Premium gets firewall rules and malware signatures in real time. The free version gets the same rules, but as the <a href=\"https:\/\/wordpress.org\/plugins\/wordfence\/\">Wordfence readme<\/a> puts it, the &#8220;free version is delayed by 30 days&#8221;. Against a median of 5 hours to mass exploitation, a 30-day delay matters.<\/li>\n<li><strong>Keep auto-updates on for plugins.<\/strong> When a fix exists, the fastest way to be safe is to have it installed.<\/li>\n<li><strong>Delete plugins you don&#8217;t use.<\/strong> A deactivated plugin&#8217;s files are still on the server. Gone is safer than off.<\/li>\n<\/ul>\n<h2>Does it slow your site down?<\/h2>\n<p>Rules only apply where the vulnerable version is actually installed, not to every site across the board. The vendors say the overhead is minimal. We haven&#8217;t measured it ourselves, so we&#8217;ll leave it at that.<\/p>\n<h2>It doesn&#8217;t replace updating<\/h2>\n<p>This is the bit worth remembering. A virtual patch is removed when you update the plugin, by design. It buys you time between disclosure and the moment you install the real fix, which, when nearly half of vulnerabilities have no fix at disclosure, is valuable time. But the real fix is still the update. With more plugins arriving all the time (we looked at <a href=\"https:\/\/jnkplugins.com\/blog\/wordpress-plugin-submissions-2026\/\">this year&#8217;s plugin submission numbers<\/a> separately), keeping the plugin list short and current is still the job.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>What is virtual patching in WordPress?<\/h3>\n<p>Virtual patching is a firewall rule written for one specific known vulnerability in one specific plugin or theme version. It is applied only to sites where that version is installed, and it blocks exploit requests without changing the plugin&#8217;s code. The rule is removed automatically once the plugin is updated or deleted.<\/p>\n<h3>Does virtual patching replace updating plugins?<\/h3>\n<p>No. A virtual patch buys time between disclosure and the real fix, which matters because 46% of WordPress vulnerabilities had no vendor fix at disclosure. Once a fix exists, update. Virtual patching also can&#8217;t stop stolen keys or bugs in PHP itself.<\/p>\n<h3>Is Wordfence free enough?<\/h3>\n<p>It helps, but its firewall rules and malware signatures are delayed by 30 days, while heavily targeted flaws were mass-exploited in a median of 5 hours. Wordfence Premium gets the rules in real time. If your host includes virtual patching, that covers the gap too.<\/p>\n<p><script type=\"application\/ld+json\">\n{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"What is virtual patching in WordPress?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Virtual patching is a firewall rule written for one specific known vulnerability in one specific plugin or theme version. It is applied only to sites where that version is installed, and it blocks exploit requests without changing the plugin's code. The rule is removed automatically once the plugin is updated or deleted.\"}},{\"@type\":\"Question\",\"name\":\"Does virtual patching replace updating plugins?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. A virtual patch buys time between disclosure and the real fix, which matters because 46% of WordPress vulnerabilities had no vendor fix at disclosure. Once a fix exists, update. Virtual patching also can't stop stolen keys or bugs in PHP itself.\"}},{\"@type\":\"Question\",\"name\":\"Is Wordfence free enough?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"It helps, but its firewall rules and malware signatures are delayed by 30 days, while heavily targeted flaws were mass-exploited in a median of 5 hours. Wordfence Premium gets the rules in real time. If your host includes virtual patching, that covers the gap too.\"}}]}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>On 12 November 2026, Kinsta switched on &#8220;Vulnerability Protection, powered by Patchstack&#8221; for every site it hosts. It&#8217;s included in every plan at no extra cost, \u2026<\/p>\n","protected":false},"author":1,"featured_media":773,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jnk_linkweave_no_autolink":false,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-772","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>WordPress Virtual Patching: What It Stops and What It Can&#039;t - JnK Plugins Blog<\/title>\n<meta name=\"description\" content=\"Kinsta now adds Patchstack virtual patching to every plan. We scored it against four real WordPress incidents from Oct-Nov 2026. Plus what to ask your host.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WordPress Virtual Patching: What It Stops and What It Can&#039;t - JnK Plugins Blog\" \/>\n<meta property=\"og:description\" content=\"Kinsta now adds Patchstack virtual patching to every plan. We scored it against four real WordPress incidents from Oct-Nov 2026. Plus what to ask your host.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/\" \/>\n<meta property=\"og:site_name\" content=\"JnK Plugins Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-14T05:14:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/11\/wordpress-virtual-patching-explained.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Suresh K Meena\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Suresh K Meena\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/\"},\"author\":{\"name\":\"Suresh K Meena\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#\\\/schema\\\/person\\\/601d025989fe7e0c285dd7fff36d9feb\"},\"headline\":\"Virtual Patching for WordPress: What Kinsta&#8217;s Patchstack Rollout Means, and What It Can&#8217;t Stop\",\"datePublished\":\"2026-11-14T05:14:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/\"},\"wordCount\":1825,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/wordpress-virtual-patching-explained.png\",\"articleSection\":[\"Guides\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/\",\"url\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/\",\"name\":\"WordPress Virtual Patching: What It Stops and What It Can't - JnK Plugins Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/wordpress-virtual-patching-explained.png\",\"datePublished\":\"2026-11-14T05:14:13+00:00\",\"description\":\"Kinsta now adds Patchstack virtual patching to every plan. We scored it against four real WordPress incidents from Oct-Nov 2026. Plus what to ask your host.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/wordpress-virtual-patching-explained.png\",\"contentUrl\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/wordpress-virtual-patching-explained.png\",\"width\":1200,\"height\":630,\"caption\":\"Featured card: virtual patching scored against four incidents\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wordpress-virtual-patching-explained\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Virtual Patching for WordPress: What Kinsta&#8217;s Patchstack Rollout Means, and What It Can&#8217;t Stop\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/\",\"name\":\"JnK Plugins\",\"description\":\"Guides, comparisons, and tutorials for our WordPress plugins\",\"publisher\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#organization\"},\"alternateName\":\"JnK Plugins Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#organization\",\"name\":\"JnK Plugins\",\"url\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/jnkplugins-jk-logo-512.png\",\"contentUrl\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/jnkplugins-jk-logo-512.png\",\"width\":512,\"height\":512,\"caption\":\"JnK Plugins\"},\"image\":{\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.youtube.com\\\/@JnKPlugins\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/jnkplugins\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/#\\\/schema\\\/person\\\/601d025989fe7e0c285dd7fff36d9feb\",\"name\":\"Suresh K Meena\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a4697e28623a48b2ee5ce631fb355d9e2dcc08a7ffb793cc5dd2885fe53dc4b2?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a4697e28623a48b2ee5ce631fb355d9e2dcc08a7ffb793cc5dd2885fe53dc4b2?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a4697e28623a48b2ee5ce631fb355d9e2dcc08a7ffb793cc5dd2885fe53dc4b2?s=96&d=mm&r=g\",\"caption\":\"Suresh K Meena\"},\"description\":\"Suresh has been building web apps for over 15 years and is the founder of JnK Plugins, where he makes honest, no-bloat WordPress tools that keep your data in your own hands. Away from the keyboard he is usually at a chessboard, thinking a few moves ahead \u2014 and he is always ready to learn something new.\",\"sameAs\":[\"https:\\\/\\\/jnkplugins.com\"],\"url\":\"https:\\\/\\\/jnkplugins.com\\\/blog\\\/author\\\/suresh\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"WordPress Virtual Patching: What It Stops and What It Can't - JnK Plugins Blog","description":"Kinsta now adds Patchstack virtual patching to every plan. We scored it against four real WordPress incidents from Oct-Nov 2026. Plus what to ask your host.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/","og_locale":"en_US","og_type":"article","og_title":"WordPress Virtual Patching: What It Stops and What It Can't - JnK Plugins Blog","og_description":"Kinsta now adds Patchstack virtual patching to every plan. We scored it against four real WordPress incidents from Oct-Nov 2026. Plus what to ask your host.","og_url":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/","og_site_name":"JnK Plugins Blog","article_published_time":"2026-11-14T05:14:13+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/11\/wordpress-virtual-patching-explained.png","type":"image\/png"}],"author":"Suresh K Meena","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Suresh K Meena","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#article","isPartOf":{"@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/"},"author":{"name":"Suresh K Meena","@id":"https:\/\/jnkplugins.com\/blog\/#\/schema\/person\/601d025989fe7e0c285dd7fff36d9feb"},"headline":"Virtual Patching for WordPress: What Kinsta&#8217;s Patchstack Rollout Means, and What It Can&#8217;t Stop","datePublished":"2026-11-14T05:14:13+00:00","mainEntityOfPage":{"@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/"},"wordCount":1825,"commentCount":0,"publisher":{"@id":"https:\/\/jnkplugins.com\/blog\/#organization"},"image":{"@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#primaryimage"},"thumbnailUrl":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/11\/wordpress-virtual-patching-explained.png","articleSection":["Guides"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/","url":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/","name":"WordPress Virtual Patching: What It Stops and What It Can't - JnK Plugins Blog","isPartOf":{"@id":"https:\/\/jnkplugins.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#primaryimage"},"image":{"@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#primaryimage"},"thumbnailUrl":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/11\/wordpress-virtual-patching-explained.png","datePublished":"2026-11-14T05:14:13+00:00","description":"Kinsta now adds Patchstack virtual patching to every plan. We scored it against four real WordPress incidents from Oct-Nov 2026. Plus what to ask your host.","breadcrumb":{"@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#primaryimage","url":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/11\/wordpress-virtual-patching-explained.png","contentUrl":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/11\/wordpress-virtual-patching-explained.png","width":1200,"height":630,"caption":"Featured card: virtual patching scored against four incidents"},{"@type":"BreadcrumbList","@id":"https:\/\/jnkplugins.com\/blog\/wordpress-virtual-patching-explained\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/jnkplugins.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Virtual Patching for WordPress: What Kinsta&#8217;s Patchstack Rollout Means, and What It Can&#8217;t Stop"}]},{"@type":"WebSite","@id":"https:\/\/jnkplugins.com\/blog\/#website","url":"https:\/\/jnkplugins.com\/blog\/","name":"JnK Plugins","description":"Guides, comparisons, and tutorials for our WordPress plugins","publisher":{"@id":"https:\/\/jnkplugins.com\/blog\/#organization"},"alternateName":"JnK Plugins Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jnkplugins.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/jnkplugins.com\/blog\/#organization","name":"JnK Plugins","url":"https:\/\/jnkplugins.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jnkplugins.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/08\/jnkplugins-jk-logo-512.png","contentUrl":"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/08\/jnkplugins-jk-logo-512.png","width":512,"height":512,"caption":"JnK Plugins"},"image":{"@id":"https:\/\/jnkplugins.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.youtube.com\/@JnKPlugins","https:\/\/www.linkedin.com\/company\/jnkplugins\/"]},{"@type":"Person","@id":"https:\/\/jnkplugins.com\/blog\/#\/schema\/person\/601d025989fe7e0c285dd7fff36d9feb","name":"Suresh K Meena","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a4697e28623a48b2ee5ce631fb355d9e2dcc08a7ffb793cc5dd2885fe53dc4b2?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a4697e28623a48b2ee5ce631fb355d9e2dcc08a7ffb793cc5dd2885fe53dc4b2?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a4697e28623a48b2ee5ce631fb355d9e2dcc08a7ffb793cc5dd2885fe53dc4b2?s=96&d=mm&r=g","caption":"Suresh K Meena"},"description":"Suresh has been building web apps for over 15 years and is the founder of JnK Plugins, where he makes honest, no-bloat WordPress tools that keep your data in your own hands. Away from the keyboard he is usually at a chessboard, thinking a few moves ahead \u2014 and he is always ready to learn something new.","sameAs":["https:\/\/jnkplugins.com"],"url":"https:\/\/jnkplugins.com\/blog\/author\/suresh\/"}]}},"_links":{"self":[{"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/posts\/772","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/comments?post=772"}],"version-history":[{"count":0,"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/posts\/772\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/media\/773"}],"wp:attachment":[{"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/media?parent=772"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/categories?post=772"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jnkplugins.com\/blog\/wp-json\/wp\/v2\/tags?post=772"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}