Skip to content

WordPress News

Kinsta adds automatic Patchstack protection to all hosted WordPress sites

Kinsta says every WordPress site on its hosting now includes Patchstack-powered vulnerability protection at no extra cost and without setup.

Source Patchstack (opens in a new tab)
Abstract 3D shield with browser windows and document cards, symbolizing website security protection.
Illustration for this article. Generated by AI.

Kinsta says every WordPress site on its hosting platform is now protected by Patchstack automatically and at no extra cost. According to Patchstack, the protection is already included with every Kinsta plan and blocked more than 1.5 million exploitation attempts across more than 68,000 sites in its first weeks.

The new feature is called Vulnerability Protection. Patchstack says Kinsta applies protection rules automatically based on the plugins, themes, and WordPress version running on each site, so customers do not need to install, configure, or monitor anything themselves.

What changed

Kinsta launched a built-in security layer powered by Patchstack for all of its hosted WordPress sites. The system checks each site against Patchstack’s vulnerability database, identifies known vulnerabilities that affect that specific site, and sends a mitigation rule only to that site at the WordPress application layer.

Patchstack says the rule blocks exploit attempts without changing plugin or theme code. If the vulnerable plugin is later updated or removed, the mitigation rule is automatically removed too. Kinsta says this is now part of every hosting plan, alongside other protections it already provides.

What it means for your website

If your site is hosted on Kinsta, this means known WordPress plugin, theme, or core vulnerabilities may be mitigated before a vendor fix is available or before you have time to test and install an update. That matters because Patchstack says many WordPress vulnerabilities are disclosed before a patch exists, and heavily targeted plugin flaws can be mass-exploited very quickly.

For business owners, the practical point is simple. Automatic mitigation can reduce exposure during the gap between public disclosure and a safe update. It does not replace updates, but it can help cover the period when your team is still reviewing, testing, or scheduling changes.

What to do now

  • If your site is on Kinsta, confirm that Vulnerability Protection is active on your plan and note that it is included automatically.
  • Keep WordPress core, plugins, and themes updated, because mitigation blocks attacks but updates still fix the underlying issue.
  • Review your plugin list for older or abandoned tools, since Patchstack says plugins account for most WordPress vulnerabilities.
  • Use staging before pushing important plugin updates live, especially when a vulnerability has just been disclosed.
  • Monitor hosting and security announcements from your provider so you know what protections are built in and what still depends on your own update process.