On this page (7 sections)
Kinsta, a managed WordPress host, has announced that every WordPress site on its platform is now covered by Vulnerability Protection, a feature powered by Patchstack. According to Patchstack's announcement, it is included in every plan at no extra cost and needs nothing installed or configured by the customer.
This matters to Kinsta customers, to agencies that manage many client sites, and to anyone comparing hosts. It is also a useful case study in what virtual patching can and cannot do. Note that the only source so far is Patchstack itself, which is the technology vendor behind the feature, so the figures below are the vendor's own claims.
What was announced
Per Patchstack, Kinsta checks the plugins, themes and WordPress version on each hosted site against Patchstack's vulnerability database. When a site runs an affected version, a protection rule is sent to that site only. Kinsta's CEO Jon Penland is quoted as saying the company identifies which vulnerabilities affect a customer's site and applies protection automatically.
Patchstack says this sits on top of protections Kinsta already offered: isolated containers, Cloudflare-powered DDoS protection, a managed edge firewall, and Bot Protection, which launched in June.
How virtual patching works
Virtual patching means blocking the exploitation of a known flaw without editing the vulnerable code. Instead of waiting for the plugin author to ship a fix, a rule inspects requests at the application layer and stops the ones that match the flaw. Patchstack describes a three-step flow:
- Identify: the host continuously matches each site's plugins, themes and WordPress core version against a vulnerability database.
- Mitigate: if the site runs an affected version, a rule is delivered to that site and no others.
- Hold the line: the rule blocks exploit attempts without changing plugin or theme code, and it is removed automatically once the plugin is updated or deleted.
Patchstack says the rules draw on its own research, a private bug bounty program and direct disclosures from plugin developers, and that it maintains more than 14,000 mitigation rules.
Why vendors are pushing this now
The announcement leans on figures from Patchstack's own State of WordPress Security in 2026 report. These are the vendor's numbers, and we have not been able to check them against another source:
- new WordPress vulnerabilities found in 2025, up 42% year over year (Patchstack)
- 11,334
- share of vulnerabilities in plugins (Patchstack)
- 91%
- of 2025 disclosures had no vendor fix at disclosure (Patchstack)
- 46%
- median time to mass exploitation of heavily targeted plugin flaws (Patchstack)
- 5 hours
If those numbers hold, the practical point is clear: for a large share of disclosures there is no update to install, and for the most targeted flaws the window to patch manually is very short. A rule that closes the gap while a fix is tested or written is the argument for virtual patching.
What this does not change
Virtual patching reduces exposure; it does not remove the vulnerability. Patchstack itself says site owners still need to keep software updated, because mitigation closes the window and updates fix the root cause. Some limits are worth keeping in mind:
- Coverage depends on a flaw being known and a rule existing for it. Unknown or undisclosed flaws are not covered by a database lookup.
- The 1.5 million blocked attempts figure comes from the vendor and does not say how many were real attacks versus scans, or how many would have succeeded.
- Protection is tied to the host. If you migrate away, the rules do not come with you, so the underlying plugins still need to be current.
- Abandoned plugins are mitigated only for known issues. Patchstack says known vulnerabilities in plugins that never get patched are mitigated while you plan a replacement, so the replacement still needs to happen.
What to do now
Whether or not you host with Kinsta, use this as a prompt to review how your own sites handle the gap between disclosure and update.
- If you are a Kinsta customer, confirm in your Kinsta account or with support how Vulnerability Protection appears for your sites and what it covers.
- Keep updating plugins, themes and WordPress core on your normal schedule. Treat virtual patching as a stopgap for the gap before an update, not a replacement for it.
- Remove plugins and themes you do not use, and plan replacements for any that are abandoned.
- Test updates on staging first; Patchstack notes a protected site can wait for a fix to be tested before it goes live.
- If you host elsewhere, ask your provider whether it offers virtual patching or a web application firewall, and what rule coverage it has.
- Check your installed plugins against the list of known plugin vulnerabilities and update or replace any that are affected.
Monitoring after the change
A protection layer is easier to trust when you can see what surrounds it. Keep an eye on certificate expiry, DNS changes and security headers, which plugin-level rules do not manage for you. Webforta's monitoring covers uptime, certificate, DNS and header changes, and the free security headers checker shows what your site sends today.
For baseline hardening that applies on any host, the WordPress security checklist is a good starting point.
The bottom line
Bundling virtual patching into hosting is a sensible response to a landscape where, by Patchstack's numbers, many flaws arrive without a fix and are exploited within hours. It lowers the cost of being slow, particularly for agencies with large portfolios. It is still one layer. Updates, plugin hygiene and independent monitoring remain the foundation, and the headline numbers should be read as a vendor's claims until others test them.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
