WordPress logo floating on dark blue water, partially submerged and surrounded by ripples, symbolizing a website presence.

Why I Stopped Relying on WordPress Themes

I’m not saying I’m perfect, but over the years I’ve learned to COMPLETELY dump wordpress themes for 2 major reasons.

Both 1 and 2 share a problem and that is you rely on a third party company to make security and functional updates. The more plugins you have, the more companies you rely on and often times, you get weird plugins in there with so few installs that you know they are going to be abandoned in a year.

My Plugin Philosophy

Downloads
1000 +

Earlier Approach

Back when wordpress was solely dominated by template and had no all in one systems, my rule of thumb was a plugin needed 10,000+ active installs or I wouldn’t use it.

Current Approach

Now I prefer even more, often only going for 100,000 – 1,000,000 or more and I’ve ditched as many plugins as I can.

Downloads
10000 +

The Problem with Too Many Plugins

Supposedly the norm is having 20-30 plugins, which is absurd. Imagine the security problem you’ll have and the lag loading in 20-30 different js functions and stylesheets (even if you merge them all).

Real-World Risk & Experience

Recently there was a big hack, for lack of a better word, affecting over 400,000 sites. In the past, I’ve used some of those plugins, but fortunately got out of that mode by attending plugins anonymous to cure me of WordPress plugin addiction. Just kidding, I’ve always hated overloading sites with plugins.

By adopting plugin minimalist, with the exception of experimenting with my own site, I’ve managed to avoid all the hacking scandals, for now. I will say though, recently a contractors computer got hacked. Fortunately I have security measures in place that alerted me and I was able to avoid a bigger issue, then implement very strict security measures.

If you’d like a fast site that has minimal security holes and doesn’t rely on plugins published from around the world, let me know. I’m happy to help!

Recent News & References

WordPress Supply Chain Attack via Flippa Plugin Purchase

Backdoored WordPress Plugins Affect Thousands of Websites

Essential Plugin Attack Breakdown

From the Essential Plugin attack:

Multiple plugs and adapters are overloaded in a wall socket, with tangled cables snaking out like a website's busy network.

The Broader Plugin Security Picture (Patchstack 2026 Report)

  • 91% of new vulnerabilities were found in plugins. There were only 6 vulnerabilities reported in WordPress core — all low priority. The problem isn’t WordPress. It’s plugins. (Patchstack 2026)
  • 250+ new plugin vulnerabilities are disclosed every week — about 36 per day. Wordfence blocks 55 million exploit attempts and over 6.4 billion brute force attacks every single month across its network. (Hide My WP Ghost, sourcing Patchstack 2026)
  • The median time from public disclosure to mass exploitation is 5 hours. Traditional advice to “just keep plugins updated” assumes you have time to act — often you don’t. (DEV Community, sourcing Patchstack 2026)
  • More than half of plugin developers (52%) who were notified of vulnerabilities did not patch the issue before public disclosure. So even “maintained” plugins frequently stay broken after the hole is public knowledge. (Patchstack 2026)
  • 46% of vulnerabilities had no developer patch when disclosed, and 43% can be exploited without any authentication — no login, no stolen password, just a vulnerable plugin sitting active on your site. (Colorlib, sourcing Patchstack 2026)

The Hidden Cost of Plugin Risk

The Abandonment Problem

827 plugins and themes were abandoned in 2024 alone, creating permanent security blind spots. Your instinct about low-install-count plugins being ticking time bombs is exactly right. (SiteGuarding)

The Financial Cost

The average total recovery cost for a small business after a WordPress compromise is $14,500 — versus roughly $8/month for proactive protection. (DEV Community, sourcing Colorlib/Xictron 2026)

Final Takeaway

The stat that might land hardest in your post is the 52% non-patch rate — over half of plugin developers who knew about a hole in their code didn’t fix it before it went public.

Share this: