Your WordPress site has a five-hour window: 8 security fixes most owners skip
That figure comes from Patchstack's State of WordPress Security in 2026 report, published in March. Most small business owners update their plugins when they remember, which tends to mean monthly, or when something looks broken. Five hours and a monthly habit do not sit comfortably together.
The report counted 11,334 new vulnerabilities in the WordPress ecosystem during 2025, up 42% on the year before. Almost none of them were in WordPress itself.
What the 2025 numbers show
91% of new vulnerabilities were in plugins and 9% in themes.
WordPress core accounted for just six, all rated low risk. The platform is not the weak point. What you install on it is.About 45% of heavily exploited vulnerabilities were attacked within 24 hours.
20% within six hours, and 70% within a week. Updating once a month leaves most of the exposure window wide open.Nearly half of reported flaws had no patch available when they were disclosed.
Keeping everything updated is necessary and, for that half, not sufficient. There is sometimes nothing to update to.Common hosting defences blocked only 12% of WordPress-specific attacks.
Patchstack tested internal firewalls, Cloudflare, Imunify360 and ModSecurity. Across broader vulnerability types the figure was 26%. Coverage of the report summarises the testing.Exploiting vulnerabilities is now the most common way into a network.
Verizon's 2026 Data Breach Investigations Report found it accounted for 31% of initial access, overtaking stolen credentials.
An honest caveat: Patchstack sells vulnerability protection, so it has an interest in the problem looking serious. The core figures are counts of published vulnerabilities, which are checkable, and they line up with what independent security researchers report. The firewall testing is Patchstack's own, and worth reading as one vendor's measurement rather than the final word.
1. List every plugin and theme, then remove what you do not use
Every installed plugin is code that can contain a flaw, whether or not it is switched on. Deactivated plugins can still be exploited on some setups, and themes you tried once in 2022 are still sitting in the folder.Open your plugins list and ask of each one: what does it do, and would anyone notice if it disappeared? Delete the ones nobody can answer for. Do the same for themes, keeping only the active one and a default fallback. The cheapest vulnerability to fix is the one in software you no longer run.
2. Turn on automatic updates where it is safe
WordPress supports automatic updates for plugins and themes, and for most small sites, switching them on for well-maintained plugins closes the five-hour gap better than any manual routine.The exceptions are plugins that run your shop, your bookings or your payments, where an update that breaks something costs money. For those, update quickly but deliberately, ideally on a staging copy first. For everything else, let the updates run.
3. Watch vulnerability disclosures, not just update notices
If nearly half of flaws have no patch at disclosure, an update notification will not tell you that you are exposed. A vulnerability alert will.Use a security plugin or service that checks your installed plugins against a vulnerability database and alerts you when one is affected. When a flaw has no fix, the options are to remove or disable the plugin until a patch arrives, or to put a targeted virtual patch in front of it. Knowing is the prerequisite for either.
4. Do not assume your host has it covered
Hosting companies market their firewalls, and those firewalls do stop a great deal of generic malicious traffic. Patchstack's testing suggests they catch a small share of attacks aimed at specific WordPress plugin flaws.That is not an argument against host-level security. It is an argument against treating it as the whole plan. Ask your host what their firewall actually covers for WordPress plugins, and assume the answer is less than the sales page implied.
5. Lock down the accounts that can change things
Many attacks do not need a sophisticated flaw. They need a weak administrator password, an old staff account nobody removed, or a contributor role with more power than it needs.Turn on two-factor authentication for every account that can edit content or install software. Remove accounts belonging to people who have left. Give each person the lowest role that lets them do their job. Limit login attempts, and change the default admin username if your site still has one.
6. Back up off the server, and test a restore
A backup stored on the same server as your site is lost along with it. A backup you have never restored is a hope rather than a plan.Keep automated daily backups somewhere separate from your hosting, retain several weeks of history so you can go back before an infection began, and restore one to a test environment at least once. The day you find out your backups do not work should not be the day you need them.
7. Use a staging site for updates that could break things
The main reason people delay updates is fear of breaking the site. A staging copy removes most of that fear.Apply significant updates to staging first, check the pages that matter, then push them live. Many hosts provide one-click staging now. It turns updating from a gamble into a routine, which is the only way updates actually happen on time.
8. Make one person responsible
Most compromised small business sites were not attacked because they were interesting. They were attacked because nobody was watching and the software was old.Security on a WordPress site is not a one-off setup. It is a small, regular job: reviewing alerts, applying updates, checking backups, removing what is no longer needed. Give it to a named person or a maintenance provider, with a schedule, and make sure someone knows what to do on the day something goes wrong.
WordPress is not the problem
It is worth being fair to WordPress here, because headlines about rising vulnerability counts tend to blur an important distinction. The core software had six reported vulnerabilities in 2025, all low risk. It is maintained by a large, experienced security team and updates itself automatically for minor releases. Run on its own, it is a well-defended platform.
The exposure comes from the ecosystem around it: tens of thousands of plugins and themes, written by everyone from large companies to a single developer who stopped maintaining their work years ago. That ecosystem is the reason WordPress can do almost anything, and the reason a typical small business site carries the security risk of every developer whose code it has installed.
The economics are the part most owners get wrong. Ongoing maintenance looks like a cost with nothing to show for it, because when it works, nothing happens. Recovery from a compromised site, by contrast, involves cleaning malware, restoring data, dealing with search engines that have flagged the site as dangerous, and explaining to customers what happened to their information. It is almost always more expensive and always more disruptive than the maintenance would have been.
The five-hour figure is the real argument. Attackers have automated the work of finding and exploiting new flaws. A site maintained by memory and good intentions is competing against software that never sleeps. The answer is not panic. It is automation and attention of your own.
Three checks to run this week
Count your installed plugins and themes, including inactive ones.
Then count how many you could explain to someone in one sentence. The difference is your easiest win.Check when your plugins were last updated by their developers.
WordPress shows this on each plugin's page. Anything not updated in over a year deserves a hard look, because an unmaintained plugin will not be patched when its flaw is found.Find your most recent backup and confirm where it is stored.
If the answer is on the same server, or you do not know, fix that before anything else on this list.
Twenty minutes, and you will know whether your site is being maintained or simply surviving.