hello@wpfoss.com
WordPress SecurityWebsite SecurityPlugins

Why WordPress plugins are the weakest part of your site

Nearly all WordPress security holes are found in plugins, not WordPress itself. Why that is, what it means for your site, and what to ask your developer.

By WPfoss Team

Most WordPress owners have been told two things: “keep WordPress updated” and “be careful with plugins”. The second one matters more than most people realise. When security researchers count the holes found in WordPress sites, almost none of them are in WordPress itself.

This guide explains why plugins are the weak point, what that means for a business site, and what to ask whoever looks after yours. It is written for owners, not developers.

What a plugin is, in plain words

WordPress itself, called “core”, handles the basics: publishing pages and managing users. A plugin is an extra piece of software added on top to do one more job: a contact form, a shop, a booking calendar, backups, SEO, speed. The WordPress documentation describes plugins as PHP scripts that extend what WordPress can do, and notes that many are developed by volunteers and are usually free.

That is a good thing. It is why WordPress can run a small restaurant site and a large shop with the same system. It is also the reason plugins are risky: every plugin is code written by someone else, to a different standard, and it runs inside your website with access to your pages, your visitors and often your customers’ details.

The numbers: where the holes are found

Patchstack, a company that tracks WordPress security flaws, reported in its State of WordPress Security in 2025 that 7,966 new vulnerabilities were found in the WordPress ecosystem during 2024. Of those, 96% were in plugins and 4% in themes. WordPress core had only seven.

Two things to keep in mind. First, this counts holes that researchers found and reported, not sites that were hacked. Second, a bigger number of reports does not always mean a worse situation: it also means people are looking and fixing. But the direction of the advice is clear. If you want to lower your risk, look at your plugins before you look at anything else.

Why plugins are the weak spot

You do not need the technical detail, only the reasons:

  • There are many of them. A typical business site installs a plugin for each small need, and the list grows over the years.
  • Quality varies. The WordPress documentation itself says that plugins in its directory, although tested and considered safe to use, are of varying quality and are often works in progress. Plugins from outside the directory have not had even that check.
  • Some are abandoned. The developer moves on and nobody fixes new problems. The plugin keeps working, so nobody notices.
  • Updates are not instant. A fix only helps once it is installed on your site.
  • Attackers are fast. Patchstack notes that it is common for a hole to be exploited within hours of being made public. A scripted attack on one page builder plugin began a few hours after the flaw was disclosed. The gap between “fix released” and “fix installed on your site” is where most of the danger sits.

What a weak plugin can mean for you

Plugins run with real power inside your site. When one has a hole, the outcome depends on the hole, but the cases we see described again and again are: a hidden login for the attacker, spam pages added to your site, visitors sent to scam pages, customer details exposed, or the site taken offline. If you are not sure what hacked looks like, read how to tell if your website is hacked.

Five habits that lower the risk

None of these needs technical skill to understand, though some need your developer to do them.

  1. Know what is installed. Ask for a list of every plugin and what it does. If nobody can say why a plugin is there, that is a question worth asking.
  2. Remove what you do not use. A switched-off plugin is still code on your server. The WordPress documentation shows the safe route: deactivate, then delete.
  3. Keep the rest updated. WordPress’s own guidance says to keep plugins up to date, and that updates add security fixes among other things. It also says to have a current backup before updating, because updates can sometimes break things. Since WordPress 5.5 you can switch on automatic updates for individual plugins.
  4. Be picky about where plugins come from. Prefer the official WordPress directory, and be wary of free copies of paid plugins from random sites.
  5. Check on plugins that have gone quiet. If a plugin has not been updated for a long time, ask your developer whether it is still looked after.

What to ask your developer or host

  • How many plugins do we have, and which ones are really needed?
  • Which plugins are out of date right now, and why?
  • Do we get told when a plugin we use has a known security hole?
  • Is there a recent backup, and how fast can we restore it? (See our WordPress security checklist.)
  • If a plugin is hacked at 2 a.m., who finds out, and when?

Want us to look at your plugins?

If you are not sure what is running on your site, start with the free website security checker. It looks at your site from the outside, the way a stranger would, and points out weaknesses worth fixing. It cannot see inside your dashboard, so it does not replace a proper plugin review.

For the review and the fixes, see our website security service.

Sources and further reading

  • State of WordPress Security in 2025, Patchstack. Source for 7,966 new vulnerabilities in 2024, the 96% plugins and 4% themes split, seven in core, and attacks starting within hours of disclosure.
  • Manage Plugins, WordPress.org documentation. Source for what plugins are, their varying quality, keeping them updated, taking a backup first, automatic updates from WordPress 5.5, and deactivating then deleting.

Stop impersonation. Control access. Protect your business.

Choose the service you need, or book a security review and we will help you identify the correct starting point.