That's not a coincidence.
WordPress was built for a different internet. Back then, a plugin-based, server-side CMS made sense. The threat landscape looked nothing like it does today. Now, AI tools scan thousands of WordPress sites simultaneously, hunting for weak spots, chaining small vulnerabilities into full attacks, automatically and faster than any patch cycle can keep up with.
Why WordPress plugins are your biggest security risk
You can do everything right and still get hit. Keeping plugins updated used to be good enough. Today, plugin updates have become an attack vector in themselves. Compromised at the source, before they even reach you.
There's always something that needs patching. A theme, a plugin, the core. It never really ends. At some point it stops being a maintenance task and starts being a liability.
The problem isn't how you're managing WordPress. It's that the architecture requires this much managing in the first place.
We moved to a different setup a few years ago.
DatoCMS as the content layer, Vercel for the frontend. No server to maintain. No plugins to patch. SSL and backups handled automatically. The attack surface doesn't get reduced. It disappears.
We've migrated several clients over. It's faster than most people expect, the editing experience is cleaner, and nobody has called us about a breach since.
If you're running WordPress and quietly wondering how much longer you want to keep doing this, it might be worth a conversation. We do migrations together with our AI, which means it's quicker and cheaper than you'd think.