
The short answer
- Patchstack found 91% of new 2025 WordPress vulnerabilities were in plugins.
- Back up before every update and test big updates on staging.
- Use auto-updates (available since WordPress 5.5) for simple, trusted plugins.
- Delete unused plugins and replace abandoned ones.
Plugins add features to WordPress, and they’re also where most security problems come from. According to Patchstack’s 2026 report, 91% of new WordPress vulnerabilities found in 2025 were in plugins, and 46% had no fix available when they were disclosed. Updating promptly, and safely, is one of the most important things you can do for your website.
Six tips for updating plugins safely
1. Back up before every update
Take a full backup (files and database) before updating, so you can roll back if something breaks. WordPress’s documentation recommends backing up “always before an upgrade”.
2. Read the changelog for major updates
Check what changed, especially for big version jumps, page builders, WooCommerce and payment plugins. Look for notes about required PHP or WordPress versions.
3. Test big updates on a staging site

A staging copy lets you check updates without risking the live site. Many hosts and plugins offer one-click staging.
4. Use auto-updates wisely
Since WordPress 5.5 (August 2020), you can turn on auto-updates for individual plugins and themes. They run twice a day by default and email you the results. Use them for simple, trusted plugins; update complex plugins (WooCommerce, page builders, payment gateways) manually after testing.
5. Remove plugins you don’t use
Deactivated plugins can still contain vulnerable code. Delete what you don’t need, and replace abandoned plugins that haven’t been updated in a long time.
6. Check the site after updating
Visit key pages, submit a test form, check checkout and payments, and look for layout problems on mobile.
When there’s no fix
If a plugin has a known vulnerability and no update, deactivate and replace it, or use a firewall or security service that blocks the specific attack until a fix is released.
If an update breaks your site
- Don’t panic: restore the backup, or roll back the plugin to the previous version.
- If you can’t reach the dashboard, rename the plugin’s folder in
wp-content/pluginsvia cPanel File Manager to disable it. - Check the error log and contact the plugin developer.
Choosing plugins that are easier to maintain
- Recently updated, with active support.
- Compatible with your WordPress and PHP versions.
- From reputable developers; never nulled copies.
- Fewer, well-chosen plugins rather than many small ones.
Our maintenance plans handle updates with backups and checks, from KES 5,000 per month. See also why websites get hacked.
Frequently asked questions
Is it safe to update WordPress plugins?
Yes, with a backup first. Not updating is usually the bigger risk.
Should I turn on automatic plugin updates?
For simple, trusted plugins, yes. Test complex plugins like WooCommerce and page builders before updating.
What if a plugin update breaks my site?
Restore your backup or roll back the plugin. If locked out, rename the plugin folder via cPanel to disable it.
Do deactivated plugins need updating?
Delete them if you don’t use them; inactive code can still be a risk.
Sources
- Patchstack: State of WordPress Security in 2026
- WordPress.org: Plugin and theme auto-updates
- WordPress 5.5 release (Aug 2020)
- WordPress: Backups
Facts checked on 4 November 2026. Prices and rules change; confirm current details with the provider or regulator.
About the author. John Kariuki is the founder of Kenya Website Designers in Nairobi. He builds business websites, online stores with M-Pesa payments and custom web systems, and manages domains and hosting for Kenyan businesses.
