Padlock on a laptop keyboard surrounded by coloured light trails
Cybersecurity

Your Plugins Are Your Attack Surface: Keeping WordPress Sites Safe

Nine in ten WordPress vulnerabilities are in plugins, and the worst get exploited within hours. Why it happens and the practical steps that keep your site safe.

F

Force Media Team

7 min read

Photo: FlyD on Unsplash

WordPress itself is in pretty good shape. That might surprise anyone who's had a WordPress site hacked, but the numbers are clear: the core software that millions of sites run on had just six reported vulnerabilities in 2025, none of them serious.

The problem is everything people bolt on to it. The contact form, the page builder, the slider, the SEO tool, the backup plugin someone installed in 2019 and forgot about. Every one of those is code written by a different developer, with its own update schedule and its own bugs. Together, they're where nearly all the risk lives.

This post explains why WordPress plugin vulnerabilities are such a big deal, how fast attackers move, and the routine we use to keep client sites safe.

Where the vulnerabilities actually are

Patchstack, a security company that tracks and coordinates WordPress vulnerability reports, publishes a yearly breakdown. Its State of WordPress Security in 2026 report found 11,334 new vulnerabilities across the WordPress ecosystem in 2025, and almost all of them were in add-ons:

Where 2025's new WordPress vulnerabilities were found

11,334new in 2025
  • Plugins91%
  • Themes9%
WordPress core accounted for just six vulnerabilities, a rounding error next to plugins and themes. Source: Patchstack, State of WordPress Security in 2026

And the number keeps climbing:

New vulnerabilities reported in the WordPress ecosystem each year

2023 is approximate, worked back from Patchstack's reported 34% rise in 2024. Some of the growth reflects more researchers looking, not just more bugs. Source: Patchstack, State of WordPress Security in 2025 and 2026

That last point in the caption matters. More reports partly means more people are hunting for bugs, which is a good thing. But the number of seriously exploitable flaws is rising too: Patchstack counted a 113% year-on-year jump in highly exploitable vulnerabilities in 2025.

Why plugins are such a weak spot

It isn't that plugin developers are careless. It's the structure:

  • Anyone can publish one. Thousands of plugins are maintained by one person in their spare time. Some are brilliant. Some haven't been touched in years.
  • Every plugin can do almost anything. A WordPress plugin runs with broad access to your site and database. A bug in a minor feature can expose the whole thing.
  • Abandoned plugins don't announce themselves. When a developer stops maintaining a plugin, it keeps working, so nobody notices, right up until a vulnerability is found and never fixed. In 2024 alone, Patchstack's previous report says 1,614 plugins and themes were removed from the official repository over unpatched security issues.
  • Premium isn't automatically safer. Patchstack found paid components had three times as many known exploited vulnerabilities as free ones in 2025, partly because they're harder for independent researchers to inspect.
Gloved hands typing on a laptop in the dark
Most WordPress attacks aren't personal. Automated tools scan millions of sites for one vulnerable plugin version and hit every match. Photo: Towfiqu barbhuiya on Unsplash

How fast attackers move

This is the part that changes how you should think about updates. Once a serious plugin flaw is made public, the clock is measured in hours, not weeks.

5 hrs

Median time to mass exploitation for heavily exploited WordPress vulnerabilities in 2025

Patchstack, 2026

~50%

of high-impact vulnerabilities were exploited within 24 hours of going public

Patchstack, 2026

46%

of vulnerabilities had no fix available from the developer when they were disclosed

Patchstack, 2026

  1. Day 0, morning

    A vulnerability is disclosed

    Details appear in public databases. If you're lucky, the developer has already released a fixed version.

  2. Within hours

    Automated scanning begins

    Attackers add the flaw to bots that sweep the internet for sites running the vulnerable version.

  3. Day 0–1

    Mass exploitation

    Unpatched sites are hit with spam pages, malicious redirects, hidden admin accounts or worse.

  4. Weeks later

    The owner notices

    Google flags the site, customers complain about redirects, or the host suspends the account.

The timeline above is illustrative, but it's built from the figures in the stat cards. The uncomfortable conclusion is that checking for updates "every month or so" leaves a site exposed for most of the window that matters. If you've read our breakdown of React2Shell, you'll recognise the pattern: speed of patching is what separates the sites that get hit from the ones that don't.

The routine that keeps sites safe

You don't need to be a security expert. You need a habit. Here's the order we'd tackle it in for any WordPress site:

  1. 1

    Audit what you've got

    Go to Plugins in your dashboard and look at every single one. Delete anything deactivated (deactivated plugins can still be exploited in some cases), anything you don't recognise, and anything not updated by its developer in over a year.

  2. 2

    Turn on automatic updates for plugins you trust

    WordPress has supported auto-updates for plugins and themes since version 5.5. For well-maintained plugins, the risk of an update breaking something is usually far smaller than the risk of leaving a known hole open.

  3. 3

    Get alerted about vulnerabilities

    Use a security plugin or service that tells you when a plugin you run has a known vulnerability, so you're not relying on spotting it in the news.

  4. 4

    Back up before you need to

    Daily automatic backups, stored off the server, with a restore you've actually tested. If something does go wrong, you want to be back online in an hour, not a week.

  5. 5

    Lock down logins

    Two-factor authentication for every admin account, no shared logins, and remove admin access from anyone who no longer needs it.

Every plugin you install is a promise to keep it updated. If you can't keep the promise, don't install the plugin.

Choosing plugins more carefully

Before installing anything new, spend two minutes on its page in the WordPress plugin directory:

CheckGood signWarning sign
Last updatedWithin the last few monthsOver a year ago
Tested withThe current WordPress versionSeveral versions behind
Active installsThousands or more (more eyes on the code)Very few, from an unknown developer
Support forumQuestions answered, issues resolvedUnanswered threads, complaints about security
Do you need it?Solves a real problem you can't solve otherwiseDoes one small thing a theme setting or a few lines of code could do

The best plugin, security-wise, is the one you didn't install. It is common to find sites running 30 or 40 plugins where 10 or 12 would do the job.

Your WordPress security check, this week

  • Every plugin and theme is updated, and unused ones are deleted (not just deactivated).
  • Automatic updates are on for plugins you trust.
  • No plugin on the site has gone more than a year without an update from its developer.
  • You'd be told within a day if a plugin you run had a known vulnerability.
  • Daily off-site backups exist and a restore has been tested.
  • Every admin account uses two-factor authentication.
  • WordPress core and PHP are on supported versions.

If you want the bigger picture beyond WordPress, our ransomware survival guide covers the email and backup side of keeping a small business safe.


Force Media looks after WordPress and custom-built websites for businesses in Sri Lanka, Australia and beyond, including updates, monitoring, backups and clean-ups after a hack. Ask us for a plugin audit, and we'll tell you which plugins are putting your site at risk.

Speak to our experts

From AI agents to secure, fast websites, we build technology that does real work for your business.

Get in touch
FAQ

Common Questions

Everything you need to know about working with Force Media.

Ask Us Anything
We primarily serve businesses in Sri Lanka and Australia, but our remote-first approach means we can work with clients globally.
Project timelines vary by scope. A standard website takes 2–4 weeks. Custom software projects range from 6–16 weeks depending on complexity.
Yes. All our projects include a support period, and we offer ongoing retainer packages for maintenance, SEO, and feature development.
Absolutely. We specialize in integrating with existing platforms, APIs, and legacy systems to extend their capabilities.