Is WordPress Secure? What October 2026 Showed
Yes, WordPress is secure at its core. The WordPress core software has a dedicated security team, fixes ship fast, and most sites get security releases automatically. When WordPress sites get hacked, the cause is almost never core. It’s an outdated plugin, a stolen login, or a site nobody is watching. October 2026 made that easy…

Yes, WordPress is secure at its core. The WordPress core software has a dedicated security team, fixes ship fast, and most sites get security releases automatically. When WordPress sites get hacked, the cause is almost never core. It’s an outdated plugin, a stolen login, or a site nobody is watching.
October 2026 made that easy to see. It was a rough month for software security, and most of the worst incidents didn’t involve WordPress at all. They hit the tools and hosting platforms behind “modern” sites too.
I build and maintain WordPress sites for small businesses, and I spent October watching this closely.
Key takeaways
- WordPress core is secure. In Patchstack’s 2026 report, 91% of new WordPress security vulnerabilities were in plugins and 9% in themes.
- Most hacked WordPress sites trace back to outdated plugins, stolen or forgotten logins, and nobody maintaining the site.
- October 2026’s worst incidents hit Node.js, npm, GitHub build pipelines, and modern hosting platforms, as well as WordPress.
- Sites without a database have a smaller front door, but the risk moves to the build tools and accounts. Our own Astro template had 35 known vulnerabilities after five months untouched.
- What protects any site: someone reading the advisories, prompt updates with judgment, tested backups kept off the server, and regular access reviews.
The short answer: is WordPress safe to use?
WordPress is a secure platform when someone looks after it. That’s true of every way of building a website.
The numbers back this up. Patchstack, a company that tracks WordPress vulnerabilities, publishes a yearly State of WordPress Security report. In the 2026 edition, 91% of new vulnerabilities were found in plugins and 9% in themes. WordPress core barely registers. (Patchstack, State of WordPress Security in 2026)
So the WordPress security issues people worry about are real, but they live in a few predictable places:
- Plugins and themes that fall behind on updates
- Logins: weak passwords, no two-factor, old accounts nobody removed
- Backups that don’t exist, or that nobody has ever tested
- Attention: a site where nobody reads the security advisories
WordPress is targeted more than any other platform, because it runs so much of the web. That makes it a bigger target. It doesn’t make the software weaker.
What happened in October 2026
Beam, a security research team, kept a running tracker of the month’s incidents. They called it “Black October.” (Beam, October 2026 incidents tracker)
WordPress had two serious incidents.
- Rank Math PRO (Oct 15–16): a popular SEO plugin sent a backdoor to sites through its own official update, for about 11 hours. Sites with auto-updates turned on installed it automatically. The recommended fix was to restore a backup from before the incident, then update to the patched version.
- TeamUpdraft (Oct 17–18): attackers accessed the customer database of the company behind the UpdraftPlus backup plugin. They used access keys from UpdraftCentral, its tool for managing many sites at once, to install backdoor plugins on customer sites. A backup tool’s access became the way in.
PHP had one too. PHP is the language WordPress runs on. A set of PHP bugs nicknamed PHP2Shell leaked before the fix was ready, and attacks followed (Oct 20–21). Every PHP site needed its server patched.
And the rest of the month hit everything else.
- Node.js, the runtime behind many modern sites, shipped fixes for 10 vulnerabilities on Oct 21, including one that could let an attacker run code on the server.
- npm, where Node packages come from, saw several poisoned packages, including a self-spreading worm.
- GitHub build pipelines were hijacked with stolen access tokens.
- Two hosting platforms for modern apps were breached. Zeabur lost data for 321,000 accounts in its second breach and is shutting down. At Railway, attackers reached stored secrets.
- A certificate authority issued keys weak enough that attackers could forge secure (TLS) certificates, which forced updates to Node, Go, and other tools.
Beam’s tracker lists no incidents for Astro, Vercel, or Netlify in October. But October also capped a long year. In August, Singapore’s Cyber Security Agency warned about a worm that spread through more than 1,300 npm packages. Attacks through the packages and tools modern sites are built from have been building all year.
Is a WordPress website more or less secure than a modern stack?
You may have heard that WordPress is outdated and insecure, and that a modern site built with a tool like Astro is safe by default.
There’s some truth in that. A site with no database and no server code has a smaller front door. There’s no WordPress login page to attack and no plugins running on every visit.
But a modern site is built from hundreds of third-party packages. It’s built on a developer’s laptop or a build service, then hosted on a platform. In October, every one of those layers had problems. The risk doesn’t go away. It moves upstream, to the build tools and the accounts.
We saw this ourselves. Astro is a popular choice for people leaving WordPress, and we keep an Astro starter template for lightweight, no-database sites. It had sat untouched for about five months. When we opened it in October, it had 35 known vulnerabilities, 2 of them critical.
The worst was a flaw in Astro’s image handling that a crafted image could use to run code. The fix shipped in late August, but only in the next major version. The usual one-command update couldn’t reach it. Moving up took code changes and a page-by-page check that nothing on the site had shifted. Before installing anything new, we checked all of the roughly 600 packages behind it against a malware database.
Most of those 35 issues lived in the tools that build the site, not in the pages visitors load. Nothing had broken. Nothing looked wrong. That’s the point.
Astro is a good tool, and a fair choice. So is WordPress. But neither one is safe on its own.
How WordPress sites get hacked
October’s incidents had two things in common, and they match what we see on WordPress sites every year.
Attackers mostly logged in. They didn’t break in. Beam’s tracker put it plainly: “The exploit was usually a login.” Stolen tokens, stolen keys, and accounts that should have been closed did most of the damage.
On a WordPress site, that looks like:
- Brute-force attacks on the WordPress login page, guessing passwords until one works
- Admin accounts for people who left years ago
- Hosting, FTP, or support logins that were never removed
We found one of these in October. After a routine support ticket, a host’s support team had left a full-admin login on one of our servers, with no expiry. Nobody ever used it, and we removed it. But a login like that is exactly what a phishing attack cashes in. If someone compromises the support engineer, every forgotten login like it becomes a door.
Malware arrived through official updates. Rank Math PRO’s backdoor came through its own update channel. “Only install official updates” didn’t protect anyone this month. A tested backup did.
The other common causes are older and well known: plugins and themes left unpatched for months, nulled (pirated) premium plugins, cheap hosting with no isolation between sites, and no firewall in front of the site. Most of these come down to the same thing. Nobody was watching.
How to keep your WordPress site secure
None of this is exotic. It just has to happen every week, not when someone remembers.
Someone reads the advisories. WordPress publishes security releases. Patchstack, Wordfence, and plugin developers publish vulnerability alerts. Someone needs to see them, and know which ones affect your site.
Security updates go out promptly, with judgment. Update WordPress core, plugins, and themes on a schedule. Most updates can go out right away. Some can wait a day or two, especially a big release from a plugin that has had problems before. Running the latest version of WordPress matters, but so does knowing when to wait.
Backups are tested, kept off the server, and old enough. A backup stored on the same server can be lost with it. A backup taken an hour after an infection doesn’t help. Keep several, keep them somewhere else, and restore one now and then to prove it works.
Access gets reviewed. Use strong, unique passwords and two-factor authentication for every admin. Limit login attempts. Remove accounts that aren’t used, including old developer, hosting, and support logins. When you’re done on the site, log out of the WordPress dashboard. Don’t just close the tab.
The hosting is solid. Good WordPress hosting keeps sites isolated from each other, patches the server, and runs a firewall. Managed WordPress hosting takes much of that off your plate. It doesn’t replace someone maintaining the site itself.
A security plugin helps, as one layer. A good WordPress security plugin can block bad login attempts to gain access and flag changed files. It can’t decide which update to hold, or notice an old login on your server.
What our own October looked like
None of our sites use Rank Math PRO or UpdraftCentral, so neither incident touched them. If one had, we’d have restored the pre-incident backup and then updated.
Here’s what the month did involve:
- WordPress version 7.1.3 (Oct 6, 7 security fixes) and 7.1.4 (Oct 28, 13 security fixes): we updated every site we look after.
- PHP2Shell: we patched our servers the same day the fix came out, and care plan clients got a short email explaining what happened.
- Kadence: the theme and blocks plugin many of our sites use has shipped two or three security releases a month lately. We track each release and update one site first, then decide which updates go to every site right away and which can wait.
- Access review: the forgotten support login above, found and removed.
None of it was dramatic. That’s how it should feel.
Common questions about WordPress security
Is WordPress secure out of the box?
Mostly, yes. A fresh WordPress install on good hosting is secure. Sites lose that over time, as plugins pile up, updates slip, and old logins stay open.
Are WordPress plugins and themes safe to use?
Most are, if they’re actively maintained. Choose plugins with recent updates and a real developer behind them. Use as few as the site needs. Never install nulled (pirated) premium plugins, which often come with malware built in.
How often should you update WordPress, plugins, and themes?
Check weekly. Apply security updates within a few days. Hold big feature releases briefly if the site depends on that plugin, and test them one at a time on your site first.
How do you know if your WordPress site has been hacked?
Common signs are unfamiliar admin users, pages you didn’t create, redirects to spam sites, and warnings from Google or your host. Many hacks show no sign at all, which is why monitoring matters more than checking by eye.
So, is WordPress secure?
Yes. WordPress is as secure as the care behind it, and so is every other platform. October 2026 showed that clearly.
If you run your own site, those steps (advisories, updates, backups, access) are the job you’d be taking on. That’s a fine choice if you want it, and what a website maintenance service actually includes lays out the full routine.
If you’d rather hand it off, that’s what our Website Care Plan is for. We watch the advisories, apply the updates, test the backups, and review access, so you don’t have to.
Whatever you choose, pick the platform for the site you need. Then make sure someone is watching it.
Related: Why I Stopped Building WordPress Sites (and Why I Build Them Again), the story of how I changed my mind about WordPress.



