Web DevelopmentBy 3 min read

11,334 new WordPress vulnerabilities in one year. 91% came from plugins.

WordPress runs 40% of all websites, which makes it the biggest target on the web. Patchstack's data shows the risk is almost entirely in plugins, and nearly half of them had no fix ready when the flaw went public.

Last updated · All figures cited from primary sources below

Quick answer

Security firm Patchstack recorded 11,334 new vulnerabilities in the WordPress ecosystem in 2025, a 42% increase over 2024. 91% were in plugins and 9% in themes, while WordPress core had only 6. 46% of vulnerabilities had no fix available when they were publicly disclosed.

11,334New vulnerabilities in 2025, up 42%
91%Found in plugins (9% in themes)
46%Had no fix at public disclosure
40.1%Share of all websites running WordPress

The volume keeps climbing

New vulnerabilities in the WordPress ecosystem
7,966
11,334
20242025
New vulnerabilities in the WordPress ecosystem
ItemValue
20247,966
202511,334
Source: Patchstack, State of WordPress Security 2025 and 2026

WordPress core itself is in good shape. It had only 6 vulnerabilities in 2025, all low priority. The problem is the ecosystem around it: 91% of new flaws were in plugins and 9% in themes.

Fixes are arriving later

Vulnerabilities with no fix at public disclosure (%)
No patch available
33%
46%
20242025
Vulnerabilities with no fix at public disclosure (%)
Item20242025
No patch available33%46%
Source: Patchstack, State of WordPress Security 2025 and 2026

When a vulnerability is published with no fix, every site using that plugin is exposed until the developer responds, and some never do. Of the 2025 flaws, 1,966 (17%) were rated likely to be exploited at mass scale, a 113% increase on the previous year.

What attackers target

Broken access control was the most exploited category. Among the 10 most-targeted vulnerabilities were privilege escalation, authorisation bypass, unauthenticated stored XSS and arbitrary file upload. These are the bugs that let an anonymous visitor become an admin.

WordPress share of the web (W3Techs)
Of all websites
40.1%
Of sites with a known CMS
58.6%
WordPress share of the web (W3Techs)
ItemValue
Of all websites40.1%
Of sites with a known CMS58.6%
Source: W3Techs, October 2026

How to secure a WordPress site

  • Keep plugins to a minimum. Every plugin you remove is one less thing to patch.
  • Delete plugins that haven't been updated in over a year.
  • Turn on automatic updates for minor releases and security fixes.
  • Add virtual patching or a web application firewall to cover the gap before fixes ship.
  • Give users the lowest role they need, and enforce two-factor login for admins.
  • Keep daily off-site backups and test a restore at least once a quarter.

Frequently asked questions

How many WordPress vulnerabilities were found in 2025?

Patchstack reported 11,334 new vulnerabilities in the WordPress ecosystem in 2025, up 42% from 7,966 in 2024.

Is WordPress core secure?

Largely yes. WordPress core had only 6 vulnerabilities in 2025, all low priority. 91% of vulnerabilities were in plugins and 9% in themes.

How do I secure a WordPress website?

Use as few plugins as possible, delete abandoned ones, enable automatic security updates, add a web application firewall or virtual patching, enforce two-factor login for admins and keep tested off-site backups.

Divyansh Barnwal

Divyansh Barnwal is the Founder & CEO of Sprite Genix in Delhi and works on digital communication for the National Testing Agency. He writes about cyber security, digital marketing and web development. About Divyansh →

Need help with security or growth?

Talk to Divyansh ↗