Kinsta-Patchstack integration blocks 1.5M exploit attempts across 68K WordPress sites

En bref

• Kinsta added Patchstack Vulnerability Protection through its hosting platform.
• About 68,000 WordPress sites received automatic coverage.
• Nearly 1.5 million exploit attempts were blocked in the initial weeks.
• No CVE was tied to the blocked activity.
• Severity is high because of the volume and breadth of attempts.

Kinsta has built Patchstack's Vulnerability Protection into its hosting platform, so WordPress customers receive exploit blocking without configuring a separate security layer. During the opening weeks of that arrangement, the setup stopped roughly 1.5 million exploit attempts and covered about 68,000 WordPress sites. No CVE has been assigned to the activity, which means defenders cannot rely on a CVE lookup alone to understand or prioritize the blocked traffic.

The directly affected group is WordPress sites hosted on Kinsta, but the lesson extends to any K-12 or public-sector team running WordPress. Because the safeguards are applied automatically at the hosting level, site owners may not see a plugin dashboard or manual toggle. That convenience is valuable for schools with limited security staffing, yet it can also create blind spots if administrators do not know what is being blocked or where coverage ends.

The scale matters. Millions of attempts in a few weeks point to sustained automated probing and exploitation traffic rather than a single isolated incident. Blocking at the host layer can keep malicious requests away from WordPress before they reach vulnerable themes or plugins, reducing load and exposure. Still, automatic blocking is not a substitute for patching, tested backups, multifactor authentication, and monitoring. The lack of a CVE also means public vulnerability feeds will not provide a clean narrative; teams should treat vendor telemetry and logs as the primary evidence.

Watch for updated counts and details from Kinsta and Patchstack, especially whether the blocked attempts target known components or broad scanner traffic. Organizations outside Kinsta should ask their hosting provider whether comparable protections exist. For now, the high severity reflects the volume and breadth of blocked attempts, not a confirmed compromise of the protected sites.

À faire maintenant

1. Inventory all WordPress sites and confirm whether Kinsta hosting and Patchstack Vulnerability Protection are active.
2. Turn on hosting-level exploit blocking and automatic safeguards where available; do not rely solely on a plugin.
3. Patch WordPress core, themes, and plugins promptly, and remove unused components.
4. Review blocked-request logs for repeat sources and patterns, then tune rules to reduce false positives.
5. Verify tested backups, multifactor authentication for administrators, and least-privilege accounts.
6. Monitor Kinsta and Patchstack advisories for updated counts, coverage changes, and new guidance.
7. For sites outside Kinsta, ask the hosting provider about comparable automatic protections.

Source originale

Patchstack