Ironhelm Suite

Where WordPress vulnerabilities really come from

Security3 min readBy the Ironhelm team

Over 11,000 new WordPress vulnerabilities were reported in 2025, almost all in plugins. What the data says, the 2024 supply chain attack, and what to do about it.

"Is WordPress secure?" is the wrong question. WordPress core gets a handful of minor security reports a year and fixes them quickly. Almost every WordPress site that gets hacked is hacked through something added to it.

What the numbers say

Patchstack, which runs one of the largest WordPress vulnerability databases, reported 11,334 new vulnerabilities in the WordPress ecosystem in 2025, a 42 percent increase on 2024. Of those, 91 percent were in plugins and 9 percent in themes. WordPress core accounted for only a few, all low priority.

The year before, its report put plugins at 96 percent. The exact split moves around; the conclusion does not. The risk lives in the plugins and themes you install, and the more of them you run, the more doors you have.

Not every vulnerability is equally dangerous. Many require the attacker to be logged in as at least a contributor, and many are found and fixed before anyone exploits them. The dangerous ones are those that need no login at all, in popular plugins, left unpatched.

The supply chain is part of the attack surface

In June 2024, Wordfence discovered malware inside plugins downloaded from WordPress.org itself. Attackers had logged in to plugin developers' accounts using passwords reused from other breached sites, then pushed updates that created rogue administrator accounts on every site that installed them. WordPress.org responded by forcing password resets and later required two-factor authentication for plugin authors who commit code.

The lesson for site owners is uncomfortable: even an official update can be hostile. That is why signed updates exist (we wrote about how Ironhelm signs every release) and why noticing new administrator accounts matters.

What actually reduces risk

  1. Fewer plugins. Every plugin you remove is a vulnerability you can no longer have. Audit the list twice a year and remove what is not used.
  2. Update quickly, especially security releases. Since WordPress 5.5, plugins and themes can update themselves automatically. For security fixes, the risk of waiting is usually larger than the risk of updating.
  3. Know when something is wrong. A vulnerability scanner that checks your installed versions against a database tells you about known holes before attackers find you.
  4. Watch for abandoned plugins. A plugin closed on WordPress.org, or not updated in years, will not get the next fix.
  5. Limit administrators and require two-step login for them, so a stolen password is not enough to install malicious code.
  6. Have a firewall in front to block the common exploit patterns while you update.

In Ironhelm

The vulnerability check warns when WordPress, a plugin or a theme has a known security hole, was pulled from WordPress.org or has been abandoned, and can install security fixes automatically. File integrity checks compare core and plugin files with the official copies every night, the activity log records new administrator accounts, and the firewall blocks common attacks before they reach WordPress.

Sources


Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.