Plugins are the best and worst thing about WordPress. They let a small business add booking, memberships or a multilingual setup in an afternoon. They’re also the source of most security problems and a large share of performance problems I’m asked to fix.
The trouble is that installing a plugin feels harmless. You click Install, then Activate, and something new appears in your menu. What actually happened is that you added code written by someone you’ve never met to a server that holds your customer data. It runs with full access to your database. If it’s badly written, abandoned or malicious, your site inherits that.
So before any plugin goes onto a site I manage, it goes through a short vetting process. Most of it takes five minutes. For plugins that will handle payments, user data or file uploads, I spend longer. Here’s how I do it.
First question: do you need a plugin at all?
It’s easy to reach for a plugin for every small change. Want to add a Google Analytics tag? There’s a plugin. Want to change the login logo? There’s a plugin. Want to disable comments? Several plugins.
Each one adds code, update overhead and potential risk. Some tasks are better solved in other ways:
- Small tweaks such as removing a feature or adding a tracking snippet can live in a tiny custom plugin of your own, a few lines long.
- Many layout needs can be handled with block patterns or your theme’s built-in options.
- Some features overlap with plugins you already have. Your SEO plugin may already handle redirects, for example.
My rough rule is this: if the job can be done reliably in under twenty lines of code you understand, write the code. If it needs ongoing maintenance, complex interfaces or integrations with outside services, a well-maintained plugin is usually the better choice.
The quick checks anyone can do
These don’t require any technical knowledge. If a plugin fails several of them, I usually stop here.
When was it last updated?
On the WordPress.org plugin page, look at “Last updated”. A plugin that hasn’t been touched in over a year isn’t automatically bad, since some simple plugins are just finished. But for anything complex, long silence often means the developer has moved on. When a vulnerability is found, nobody will fix it.
Also check “Tested up to”. If it’s several major WordPress versions behind, be cautious.
How many active installations?
Popularity isn’t proof of quality, but it does mean more people are using the code, reporting bugs and paying attention. A plugin with a few hundred installs and a plugin with a million installs carry different levels of risk. Smaller plugins can be excellent, they just deserve a closer look.
What do the support forums look like?
This is my favourite signal. Open the support tab and scroll through recent threads. Are people getting replies? Does the developer respond politely and fix reported bugs? Or are there pages of unanswered questions and complaints about broken updates?
A responsive developer tells you more about future reliability than a star rating does.
Read the negative reviews
Five-star reviews are often vague. One and two-star reviews tell you what goes wrong. Look for patterns. One person complaining that the plugin conflicts with their theme isn’t a red flag. Twenty people reporting that an update broke their checkout is.
Has it been closed or flagged?
If WordPress.org has closed a plugin, the page shows a notice. Plugins get closed for various reasons, including security issues that weren’t fixed. Don’t install a closed plugin, and if you already use one, find a replacement.
Check the vulnerability history
Every popular plugin has had a vulnerability at some point. That’s normal. What matters is how it was handled.
Public vulnerability databases from companies such as Wordfence, Patchstack and WPScan list known issues for each plugin. Search the plugin’s name and look at:
- How many vulnerabilities have been reported, and how serious they were.
- How quickly they were fixed after being reported.
- Whether any are still unfixed.
A plugin that had three vulnerabilities over five years, all patched within days, is in better shape than one with a single unpatched issue sitting open for months.
Premium plugins need the same scrutiny
Paying for a plugin doesn’t guarantee quality. Some premium plugins are excellent and properly supported. Others are thin wrappers sold through marketplaces with little long-term support. Before buying, look for a public changelog, a clear support policy, documentation and evidence that the company has been around for a while.
Never use nulled plugins
Nulled plugins are pirated premium plugins distributed for free. I’ll say it plainly: in my forensic work, nulled plugins and themes are one of the most reliable ways to end up with malware. The people distributing them are not doing it out of generosity. Hidden backdoors, spam link injectors and credential stealers are common. Saving the cost of a licence is never worth it.
Test it on staging first
Never install a new plugin straight onto a live site, especially a store. Install it on a staging copy and check a few things:
- Does the site still work normally, including forms, checkout and login?
- Did page load times change noticeably?
- Did it add scripts and styles to every page, even where it isn’t used?
- Did it create new database tables or add lots of autoloaded options?
The free Query Monitor plugin is perfect for this. It shows the number of database queries on each page, which component triggered them, and which scripts and styles were loaded. Compare a page before and after activation. If a simple contact form plugin adds forty queries to your homepage, you’ve learned something important.
A short code review for the curious
If you’re comfortable reading PHP, a quick look at a plugin’s code tells you a lot about the developer’s habits. You don’t need to read everything. Look for a few common patterns.
Database queries
Search for $wpdb. Any query that includes user input should use $wpdb->prepare. This is the difference between safe and unsafe:
Capability checks and nonces
Any action that changes data, such as saving settings or deleting records, should check that the user is allowed to do it and that the request is genuine. Look for current_user_can and nonce checks such as check_admin_referer or wp_verify_nonce near AJAX handlers and form processing.
Missing capability checks are one of the most common causes of plugin vulnerabilities, because they let low-level users or even visitors trigger admin actions.
REST endpoints
Search for register_rest_route. Every route should have a permission_callback that actually checks something. A callback that simply returns true is fine for public data, but alarming on an endpoint that changes settings or exposes user information.
Output escaping
When a plugin prints data to the page, it should escape it with functions like esc_html, esc_attr or esc_url. Unescaped output is how cross-site scripting bugs happen.
Red flags
Some things should make you stop immediately: base64-encoded blobs of code, eval statements, code that downloads and runs files from remote servers, or obfuscated variable names in a plugin that has no reason to hide anything.
Keep a plugin inventory
Once a plugin is approved, write it down. For each site, I keep a simple list: plugin name, why it’s installed, who requested it, and whether it’s free or licensed with a renewal date. It sounds bureaucratic, but it makes quarterly reviews painless. When you can’t remember why a plugin is installed, that’s often a sign it can go.
Review regularly
Vetting isn’t a one-time event. A plugin that was well maintained when you installed it can be abandoned later, sold to a new owner with different priorities, or start adding features you don’t want. Every few months, run through your plugin list and re-check the update history and support forums. Replace anything that has gone quiet.
Frequently asked questions
How many plugins is too many?
There’s no magic number. A site with thirty well-coded plugins can be faster and safer than one with eight bad ones. Focus on quality and purpose, not count. That said, every plugin is something to update and monitor, so fewer is easier to manage.
Are plugins from WordPress.org safe?
They’re reviewed when first submitted and the repository can close plugins with security issues, which is better than random downloads. But it’s not a full ongoing security audit. Use the checks in this guide for repository plugins too.
What should I do if a plugin I rely on is abandoned?
Start planning a replacement right away, before a vulnerability is published. Test alternatives on staging, plan how to migrate any data the plugin stores, and switch on a quiet day. If no replacement exists, a developer can sometimes maintain a private fork for you.
Is it safe to buy plugins from marketplaces?
Buying from a legitimate marketplace or directly from the developer is fine. Just check that the plugin is actively updated and supported. Avoid sites offering premium plugins at huge discounts or for free, since those are often nulled copies.
Final thoughts
Every plugin is a small trust decision. Most are perfectly fine, and the WordPress ecosystem is full of talented developers doing excellent work. But a few minutes of checking before you click Install can save you from slow pages, broken updates and, at worst, a hacked site. Treat plugins like hiring someone to work inside your business: check their track record first.




