Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Explainer

WordPress Security Statistics (2026)

Short answer

Patchstack counted 11,334 new WordPress vulnerabilities in 2025, up 42% on 2024, with 91% in plugins and only 6 low-priority flaws in WordPress core. WordPress ran 38.5% of all websites as of 19 November 2026, according to W3Techs. Heavily targeted flaws were mass-exploited within a median of 5 hours, so fast updates matter more than any single tool.

Key takeaways

  • Patchstack counted 11,334 new WordPress vulnerabilities in 2025, a 42% rise on 2024.
  • Plugins held 91% of new vulnerabilities in 2025, themes held 9%, and WordPress core had only 6 low-priority flaws.
  • Nearly half of 2025 vulnerabilities, 46%, had no developer fix when they were made public.
  • WordPress ran 38.5% of all websites and held a 57.4% share of the CMS market as of 19 November 2026.
  • Wordfence blocked 10.4 billion firewall attacks and 18.2 billion brute-force attacks in Q2 2026.
  • Sucuri found 39.1% of content management systems outdated at the point of infection in its 2023 report.

How many WordPress vulnerabilities were found in 2025?

Patchstack counted 11,334 new WordPress vulnerabilities in 2025, a 42% rise on 2024.

The count comes from Patchstack's State of WordPress Security in 2026, updated 25 February 2026. It covers flaws in WordPress core, plugins, and themes reported during 2025.

StatisticFigureSourceYear
New vulnerabilities found11,334Patchstack2025
Rise on the prior year42%Patchstack2025
WordPress share of all websites38.5%W3Techs2026
WordPress share of the CMS market57.4%W3Techs2026
Firewall attacks blocked in Q210.4 billionWordfence2026
Brute-force attacks blocked in Q218.2 billionWordfence2026
Sites with malware found in Q2573,000Wordfence2026
Infected sites found by SiteCheck1,176,701Sucuri2024

Not every entry is a live threat. Patchstack rated 4,124 of the 11,334, or 36%, as a real threat that needed a protection rule.

A further 1,966 entries, or 17%, had a high severity score and were likely targets for automated mass attacks.

Highly exploitable flaws rose 113% year on year in 2025. Patchstack found more high-severity flaws in 2025 than in the prior two years combined.

How much of the web runs WordPress in November 2026?

WordPress ran 38.5% of all websites as of 19 November 2026, according to W3Techs.

W3Techs updates its survey daily and lists WordPress at a 57.4% share of the content management market. That second figure counts only sites where a known system was found.

The same survey found 33.0% of websites use none of the systems it monitors. WordPress still leads the next system, Shopify at 5.4% of all websites, by a wide gap.

A large share means a large target. Attackers can reuse one flaw across millions of sites that run the same plugin.

Where do most WordPress vulnerabilities live?

Plugins held 91% of new WordPress vulnerabilities in 2025, and themes held 9%.

Patchstack found only 6 vulnerabilities in WordPress core in 2025, and it rated all 6 as low priority. The core is a small part of the yearly count.

That split does not mean plugins are badly built as a group. It means the risk sits where the code changes most often, in the many plugins each site adds.

Free plugins get more public review, while paid parts get less. Patchstack received 1,983 valid reports for premium or freemium parts in 2025, or 29% of its total reports.

Of those premium reports, 76% were exploitable in real attacks. Premium parts also had 3 times more Known Exploited Vulnerabilities than free parts.

A Known Exploited Vulnerability is a flaw with confirmed attacks in the wild. It is a shortlist of flaws attackers already use.

Copies from outside the official directory add risk on top of this. Read are nulled WordPress plugins safe before you install one.

How fast do attackers exploit a new vulnerability?

For heavily exploited flaws, the weighted median time to mass exploitation was 5 hours in 2025.

Patchstack measured the gap between a protection rule going out and the first exploit attempt it saw. About half of high-impact flaws were exploited within 24 hours of disclosure.

Speed matters because 46% of 2025 vulnerabilities had no fix from the developer when they were made public. Waiting for a patch leaves a window attackers use.

Old flaws stay in play too. Patchstack found only 4 of the 10 most attacked flaws in 2025 were published that year.

The rest were older flaws, still present on sites that had not updated. Patching delays compound over time.

How many attacks does a WordPress firewall block?

Wordfence blocked 10.4 billion firewall attack requests in Q2 2026, up 14.3% on the prior quarter.

The figure comes from Wordfence's Q2 2026 threat report, published 29 September 2026. It counts requests stopped by its firewall across the sites it protects.

The same quarter saw 18.2 billion brute-force attacks blocked, up 13.8% on Q1 2026. Brute-force attacks are repeated login guesses, not confirmed logins.

Wordfence also logged 19.7 million unique IP addresses in firewall attacks during Q2 2026, up 16.7% on the prior quarter.

Blocked requests are not hacked sites. They show attack volume on protected sites, and a single attacker can send thousands of requests.

A firewall rule can block a known flaw before a patch ships. See how to set up the Wordfence firewall for the settings to check first.

What happened with the WordPress core flaw in October 2026?

Wordfence blocked over 240,000 exploit attempts against one WordPress core flaw after it was disclosed on 28 October 2026.

Wordfence's report on the flaw says it affects WordPress core versions 4.7 through 7.1.3 and carries a CVSS score of 8.1. WordPress fixed it in version 7.1.4, released 28 October 2026.

Attacks began the same day the flaw was disclosed. The peak came on 30 October 2026, when Wordfence blocked over 74,000 attempts in a single day.

The US Cybersecurity and Infrastructure Security Agency added the flaw to its Known Exploited Vulnerabilities catalog on 2 November 2026. That listing marks flaws with confirmed exploitation.

This case shows why core updates deserve fast action. A core flaw is rare, but when one appears, scanning starts within hours.

What malware do hacked WordPress sites carry?

Malware and malicious redirects caused 74.7% of infections Sucuri found in 2024.

The figure comes from Sucuri's SiteCheck Malware Trends Report 2024, based on 70.8 million scans. It found 1,176,701 infected websites, an infection rate of 1.66%.

SEO spam caused 38.4% of infections in the same report, affecting 422,741 websites. SEO spam is hidden text or links that push spam pages in search results.

Wordfence reported 573,000 sites with malware detected in Q2 2026, up 21.0% on the prior quarter. That count covers sites in its protected population only.

Attackers now hide code inside real files instead of adding new ones. Patchstack and Monarx found injected code in real core, plugin, and theme files is getting harder to find and remove.

If a site is already infected, cleanup cost varies by size and damage. See what it costs to clean a hacked WordPress site before you pick a route.

How often are hacked sites out of date?

In Sucuri's 2023 hacked website report, 39.1% of content management systems were outdated at the point of infection.

Sucuri's 2023 hacked website report counted a system as outdated when it lacked the latest security release at cleanup time. WordPress automatic updates helped keep its share lower than other systems.

The same report found at least one vulnerable plugin or theme on 13.97% of compromised sites. Outdated code and known flaws often appear together on one site.

Malicious admin users were found in 55.2% of infected WordPress databases in that report. An extra admin account lets an attacker return after a cleanup.

WordPress accounted for 95.5% of the infected sites Sucuri's team cleaned in 2023. That share tracks its share of the web more than any single flaw in the core.

Old plugins that no longer get updates are a common source of known flaws. See how to find abandoned WordPress plugins to check yours.

What types of flaws are reported most often?

Cross-site scripting led Wordfence's Q2 2026 list, with 600 new entries.

Cross-site scripting, or XSS, lets an attacker inject scripts into pages other people view. Wordfence counted it as the top class in Q2 2026.

  • Cross-site scripting: 600 entries in Q2 2026
  • Missing authorization: 416 entries in Q2 2026
  • SQL injection: 213 entries in Q2 2026
  • Cross-site request forgery: 121 entries in Q2 2026
  • Deserialization of untrusted data: 103 entries in Q2 2026

Missing authorization means a user can reach an action they should not have. SQL injection means attacker input can change a database query.

Patchstack's most exploited class in 2025 was broken access control. It is hard for a basic firewall to spot because the requests look like normal logged-in traffic.

Wordfence added 2,073 vulnerabilities to its database in Q2 2026, down 24.3% on Q1, while high-threat entries rose 15.2% to 182.

At the end of Q2 2026, 149 vulnerabilities in the Wordfence database still had no patch. A scanner that flags unpatched flaws helps you remove or replace the software.

What do the numbers mean for your site?

The numbers point to plugins, patch speed, and logins as the three areas that matter most.

First, keep the plugin list short and current. Most new flaws live in plugins, and nearly half arrive with no fix ready.

Second, update fast when a high-impact flaw is disclosed. The median wait to mass exploitation was 5 hours for heavily targeted flaws in 2025.

Third, guard logins. Brute-force blocks ran to 18.2 billion in one quarter, and malicious admin users were found in 55.2% of infected databases in Sucuri's 2023 report.

Do not add vendor totals together. Patchstack counted 11,334 new flaws in 2025, while Wordfence counted 2,073 in one quarter of 2026. Each vendor counts from its own database, so the totals measure different things.

Treat blocked-attack counts the same way. They measure requests stopped on protected sites, not sites that were hacked.

What mistakes should you avoid?

The main mistake is treating a single number, like a total flaw count, as a count of hacked sites.

  • Reading blocked requests as hacked sites: blocked requests show attack volume, not successful break-ins.
  • Waiting for a monthly update cycle: heavily targeted flaws were mass-exploited within 5 hours in 2025.
  • Keeping plugins you no longer use: unused plugins still carry flaws and still need updates or removal.
  • Ignoring extra admin accounts: Sucuri found malicious admin users in 55.2% of infected databases in 2023.
  • Trusting a firewall alone: Patchstack's 2025 pentest found common defences blocked only 26% of vulnerability attacks in its expanded test.

If you want outside help, compare options first. Sucuri security pricing is one reference point for managed cleanup and firewall costs.

Frequently asked questions

How many WordPress sites get hacked each year?

No public source gives a reliable yearly count of hacked WordPress sites. Vendors measure different things: Patchstack counted 11,334 new flaws in 2025, Wordfence counted blocked requests, and Sucuri found 1,176,701 infected sites in 70.8 million scans in 2024. Those figures describe flaws, attacks, and cleanups, not a single total of hacked sites.

Is WordPress itself insecure?

WordPress core is a small part of the yearly flaw count. Patchstack found only 6 core vulnerabilities in 2025, all rated low priority, while plugins held 91% of new flaws. The risk sits mainly in the plugins and themes each site adds, and in how fast those parts get updated.

How quickly should I update after a security release?

Update within hours when a high-impact flaw is disclosed. Patchstack found a weighted median of 5 hours to mass exploitation for heavily targeted flaws in 2025, and about half of high-impact flaws were exploited within 24 hours. Turn on automatic updates for minor core releases so routine fixes apply without delay.

Do I need a security plugin if my host has a firewall?

A host firewall alone is not enough. Patchstack tested common defences in 2025 and found they blocked only 26% of vulnerability attacks in its expanded test. Pair a firewall with fast updates, a short plugin list, login protection, regular scans, and backups kept off the server.

What should I check first on my own site?

Start with the plugin list: remove what you do not use and update the rest. Then check for extra admin accounts, confirm core and PHP are current, and make sure a recent backup exists off the server. Sucuri found malicious admin users in 55.2% of infected databases in 2023, so the user list is worth a close look.

Sources

  1. State of WordPress Security in 2026 Patchstack
  2. Usage Statistics and Market Share of Content Management Systems W3Techs
  3. Quarterly WordPress Threat Intelligence Report – Q2 2026 Wordfence
  4. Attackers Actively Probing for Upgrade-Window RCE Vulnerability in WordPress Core Wordfence
  5. 2023 Hacked Website & Malware Threat Report Sucuri
  6. SiteCheck Malware Trends Report 2024 Sucuri

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test