Safe WordPress updates: plugins, themes, and core

Why updates deserve a routine of their own

Updates are the most important maintenance task on a WordPress site, and the one site owners fear most. Skip them, and you leave known security holes open. Rush them, and a single incompatible plugin can take down a checkout page on a Friday afternoon.

The risk is real on both sides. Patchstack's research shows that the most heavily targeted WordPress vulnerabilities are exploited within hours of being made public, so waiting weeks for a convenient moment is no longer safe. At the same time, plugins, themes, and WordPress itself change constantly, and not every combination works together on day one.

The good news is that WordPress now does much of the safety work for you, and a simple routine covers the rest. This guide explains what gets updated, what to automate, how to update by hand without drama, and how to recover when something breaks. It is part of our WordPress maintenance series.

What actually gets updated

A WordPress site has five moving parts, and each carries a different level of risk.

ComponentHow oftenTypical riskNotes
Core, minor releases (for example 7.1.1 to 7.1.2)Several times a yearLowSecurity and bug fixes only. Updates itself automatically by default.
Core, major releases (for example 7.0 to 7.1)Two or three times a yearMediumNew features, editor changes, sometimes raised server requirements.
PluginsConstantlyLow to highThe biggest source of both vulnerabilities and conflicts. Risk depends on how central the plugin is.
ThemesOccasionallyMediumCan change layouts. Customisations made directly in the theme are overwritten.
TranslationsConstantlyVery lowLanguage files; they update automatically by default.

The server's PHP version sits underneath all of this. It is not updated from wp-admin, but it matters just as much, and we cover it later in this guide.

The risk in the table is not about the update itself. It is about what depends on it. A minor update to a contact-form plugin is low stakes. A major update to WooCommerce, a page builder, or a membership plugin touches the parts of the site that make money, and deserves a test first.

Before you update

Four checks turn a risky update into a routine one. Together they take a few minutes.

  1. A fresh backup, files and database. Not last week's: one taken right before you start, stored off the server, from a tool you have actually restored with before. A backup you have never tested is a hope, not a plan.
  2. A staging site for anything big. Staging is a private copy of your site where you can update and click around without affecting visitors. Many hosts create one in a click. Use it for major core releases, major versions of key plugins (version numbers like 9.x to 10.0), theme updates, and PHP upgrades.
  3. A look at the changelog. Every plugin page on WordPress.org has a Changelog tab, and commercial plugins publish release notes. Look for the words "breaking change", "requires", "removed", or "database update". A fix that says "security" means update soon.
  4. A compatibility check. Each plugin lists the WordPress version it was tested up to and the minimum PHP it needs. Right after a major WordPress release, give your key plugins a few days to confirm compatibility, unless a security fix is involved.

Then pick your moment: a quiet time of day, not right before a campaign launch or a weekend, and when you have half an hour to check the site afterwards. That last part is the one people skip.

Auto-updates: what to automate and what to hold

Auto-updates used to be a gamble. They are much safer now, thanks to protections WordPress has added in recent years:

  • Minor core releases have updated themselves automatically for years. Leave this on.
  • Plugin and theme auto-updates can be switched on one by one, from the "Enable auto-updates" link on the Plugins and Themes screens.
  • Rollback on failure. Since WordPress 6.6, when a plugin auto-update causes a fatal error on the front end, WordPress detects it, restores the previous version, and emails the site admin. Since 6.3, a manual plugin or theme update that fails mid-install is also rolled back automatically.

These safeguards catch crashes, not everything. A plugin can update without a fatal error and still break a layout, a form, or a payment step. That is why auto-updates suit some plugins better than others.

Turn auto-updates onHold for a manual update
Minor core releases (default)Major core releases on business-critical sites
Security plugins, SEO plugins, small utility plugins from reliable developersWooCommerce and its extensions, payment gateways
Plugins that release frequent small fixesPage builders and the active theme
Translations (default)Membership, booking, and LMS plugins

The logic behind this split is the rule for the whole guide: update small and often, and test the big ones first. A site that applies small updates every few days rarely faces a frightening update day, because no single update carries months of changes.

One more point: auto-updates do not replace a backup. Set your backup tool to run daily, so there is always a recent copy to fall back on.

A safe manual update routine

For the updates you hold back, follow the same order every time.

  1. Back up. Trigger a fresh backup and confirm it finished.
  2. Test on staging if the update is major or touches checkout, forms, or layout. Repeat the steps below there first.
  3. Update in the right order: plugins first, then the theme, then WordPress core. Plugins usually add support for a new WordPress version before it ships, so updating them first avoids running old plugin code on new core.
  4. Update one key plugin at a time. Batch the small ones if you like, but update WooCommerce, the page builder, or the membership plugin on its own, so you know exactly what caused a problem.
  5. Run any database update. WooCommerce and some other plugins show a notice asking to update the database after a new version. Do it straight away, after the backup.
  6. Clear the caches: your caching plugin, the host's server cache, and the CDN, so you test the new version and not a stored copy.
  7. Check the site in a private browser window. Open the homepage, a key service or product page, a contact form, and the checkout or booking flow. Submit a test form. Glance at the browser console for errors if you know how.
  8. Write it down. Note what you updated, from which version to which, and anything odd. That log is what makes troubleshooting quick next month.

If you manage sites from the command line, WP-CLI does the same work: wp plugin update --all --dry-run lists what is pending, and wp plugin update woocommerce updates a single plugin.

Themes: protect your customisations first

A theme update replaces the theme's files completely. Any change made directly inside those files (an edited template, a line added to functions.php, CSS pasted into style.css) disappears the moment you update.

That is why customisations belong somewhere else:

  • A child theme holds your template and code changes and inherits everything else from the parent theme. The parent can then update freely.
  • Additional CSS in the Customiser, or the Styles panel in block themes, stores style changes in the database, not in theme files.
  • A small custom plugin or a snippets plugin is the right home for functions that should survive a theme switch.

Before updating a theme you did not build, check for direct edits. If you inherited the site, compare the theme folder against a fresh download of the same version, or ask whoever built it.

Two special cases:

  • Premium themes often update through their own licensing system, not WordPress.org. An expired licence usually means no updates, including security fixes. Keep licences active for the theme and any premium plugins.
  • Block themes store many template edits made in the Site Editor in the database, so theme updates do not overwrite them. But edits saved in the database also stop receiving the theme author's improvements to those templates. If a template looks outdated after an update, check whether it has been customised and reset it if appropriate.

When an update goes wrong

Stay calm. Almost every broken update can be undone in minutes if you work through the options in order, from lightest to heaviest.

1. The site shows "There has been a critical error on this website." This is WordPress's fatal error protection, in place since version 5.2. WordPress emails the site admin a link to log in using Recovery Mode, where the faulty plugin or theme is paused for you so you can reach the dashboard. Deactivate the culprit, then exit Recovery Mode. Keep the admin email address on the site current, or this email goes nowhere.

2. No email, no dashboard. Connect with your host's file manager or SFTP and rename the plugin's folder inside wp-content/plugins (for example, add -off to the end). WordPress deactivates it automatically. With WP-CLI: wp plugin deactivate plugin-name.

3. The site works but something is broken. Roll back the plugin to the previous version. WordPress itself does not keep old versions after a successful update, but WP-CLI can install a specific one (wp plugin install plugin-name --version=2.4.1 --force), and rollback plugins do the same from the dashboard. Report the problem to the plugin developer, then wait for a fixed release before updating again.

4. Several things broke, or the database changed. Restore the backup you took before you started. If a plugin ran a database update, rolling back its files alone may not be enough, which is exactly why the backup comes first.

Afterwards, add a line to your maintenance log: what broke, which version, and how you fixed it. Patterns show up quickly.

The updates you can't install: abandoned plugins and old PHP

Plugins that stopped updating

The most dangerous plugin is not the one with frequent updates. It is the one that never updates. If a vulnerability is found in an abandoned plugin, no fix is coming.

Once a quarter, scan your plugin list for warning signs:

  • No update in a year or more.
  • A WordPress.org page warning that the plugin has not been tested with recent major releases of WordPress.
  • A plugin that has been closed on WordPress.org. The directory page says so; closures often follow an unfixed security issue.
  • A premium plugin whose licence has lapsed, or whose developer has gone quiet.

For each one, decide: replace it with a maintained alternative, rebuild the feature another way, or remove it if nobody uses it. Deactivated plugins should be deleted too; their files can still be attacked.

PHP, the update below the surface

PHP is the programming language WordPress runs on, and your host sets its version. Each PHP version gets security fixes for a limited time. WordPress still runs on PHP 7.4 for backward compatibility, but WordPress.org recommends PHP 8.3 or newer, and the Hosting Team recommends PHP 8.4 or 8.5 for new installations. PHP 8.2 stops receiving security fixes on 31 December 2026, so sites still on it should plan an upgrade now.

Check your version in Tools > Site Health > Info > Server. Upgrade it like a major core release: back up, switch PHP on staging first (most hosts let you choose the version per site), test the key pages, then switch production. Old plugins and themes are what usually break, which brings you back to the list above.

Update checklist

Once, at setup

  • Daily automatic backups stored off the server, with one test restore
  • A staging site, from your host or a plugin
  • Auto-updates on for minor core releases, translations, and low-risk plugins
  • Customisations moved into a child theme, Additional CSS, or a custom plugin
  • A current admin email address, so Recovery Mode emails arrive

Every week

  • Review pending updates; apply security fixes the same day
  • Read the auto-update emails for rollbacks or failures

Every month (the updates step of the 30-minute routine)

  • Fresh backup
  • Held-back updates: staging first for major ones, then plugins, theme, core
  • Clear caches and test key pages and forms in a private window
  • Log what changed

Every quarter

  • Look for abandoned, closed, or unlicensed plugins and themes
  • Delete deactivated plugins and unused themes
  • Check the PHP version against its end-of-life date

Updates stop being stressful when they stop being events. Keep them small and often, and test the big ones first, and most updates become a non-event.

Sources

Changed