Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

How to Update WordPress, Plugins and Themes Safely

How to Update WordPress, Plugins and Themes Safely

Short answer

To update WordPress safely, check your versions, read the changelogs, and take a full backup of files and database first. Update core from Dashboard, then Updates, and update plugins and themes one at a time, checking the site after each one. The current release is WordPress 7.1.5, a security release from 18 November 2026.

Key takeaways

  • WordPress 7.1.5, released 18 November 2026, is a security release; only the most recent version is actively supported.
  • The Updates screen warns you to back up your database and files before upgrading.
  • WordPress runs plugin and theme auto-updates twice a day by default, once you opt in per plugin or theme.
  • PHP 8.2 gets security fixes only until 31 December 2026, and PHP 8.3 until 31 December 2027.
  • Update plugins and themes one at a time, and check the site after each one.

Why do WordPress updates matter?

Updates fix security holes, repair bugs and add features, so a site that skips them stays open to known attacks.

WordPress 7.1.5, released on 18 November 2026, is a security release, and WordPress recommends that sites update to it at once, as announced on WordPress News. The release fixes a set of security issues, including cross-site scripting flaws and a privilege escalation flaw that could lead to remote code execution.

Only the most recent version of WordPress is actively supported, as the same release notice states. Older branches get security backports for a time, but the fixes in 7.1.5 were backported only through version 4.7, so very old sites are on their own.

Check your version under Dashboard, then Updates. The guide to checking your WordPress version shows the other places the version appears.

What should you check before any update?

Check your WordPress, PHP and plugin versions, read the changelogs, and confirm your last backup is fresh.

Open Tools, then Site Health, and read the status page for warnings about old PHP or missing updates. WordPress needs PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.4 or newer, and HTTPS support, as listed on WordPress.org's requirements page.

Read the changelog for each plugin and theme with an update waiting. The changelog says what the update fixes, and a major version jump is a sign to check the plugin's site for breaking changes before you click update.

Confirm your backup ran in the last day and that it holds both files and the database. The Updates screen itself warns you first: "Important: before upgrading, please backup your database and files," as shown in WordPress's Dashboard Updates documentation.

How do you back up before you update?

Take a full backup of files and database, download a copy off the server, and check that the backup file is not empty.

A backup plugin can do this in a few clicks, or your host may offer backups from its panel. Either way, the backup must hold the wp-content folder and a copy of the database, since the files alone cannot rebuild your posts and settings.

Download the backup to your own computer or to cloud storage before you update. A backup that lives only on the same server as the site is no help if the server itself fails. The guide to backing up WordPress covers the plugin and manual routes in detail.

Test a restore at least once, on a staging copy or a local install, before you need it for real. A backup you have never restored is a guess, not a safety net.

How do you update WordPress core safely?

Back up, update on staging first for a major release, then click Update Now in Dashboard, then Updates, and check the site.

Open Dashboard, then Updates, and read what version is offered. For a minor security release such as 7.1.5, update the live site at once, since these releases fix known flaws.

For a major release, such as the planned 7.2 release on 8 December 2026, run it on a staging copy first, as announced on WordPress News.

WordPress applies minor core releases and translation files by itself by default, as explained in Learn WordPress's managing updates lesson. Major releases wait for you to click Update Now, so they never start without warning.

After the update, open the home page, log in to wp-admin, and check Site Health again. If the update fails halfway, WordPress may show a “briefly unavailable” message; wait a minute, then check again before you act.

How do you update plugins and themes?

Update one plugin or theme at a time, check the site after each one, and leave inactive plugins and themes out of the update.

Open Dashboard, then Updates, to see every plugin and theme with an update waiting, as described in WordPress's Dashboard Updates documentation. You can select them all and click Update, but updating one at a time makes it easy to tell which one broke the site if something goes wrong.

Update the active theme first, then the plugins your pages depend on, then the rest. Delete plugins and themes you no longer use instead of updating them, since unused code is still a risk if it holds a flaw.

If a plugin update breaks a page, roll it back from your backup or use the plugin's previous version from the WordPress.org directory. The guide to updating WooCommerce safely covers the same one-at-a-time method for stores.

Should you turn on automatic updates?

Turn on automatic updates for plugins and themes you trust, and leave major core releases and complex plugins on manual control.

Since WordPress 5.5, admins can opt in to automatic updates theme by theme and plugin by plugin, as stated in WordPress's auto-updates documentation. You turn it on from the Plugins screen, where each plugin has an Automatic update column, or from the theme details view.

WordPress runs automatic updates twice a day by default, and it sends an email when plugins or themes were updated, according to the same documentation. That email is your signal to check the site after an automatic run.

Keep automatic updates off for your page builder, your store plugin and any plugin tied to payments. Those need a staging check first, since a bad auto-update can break checkout while you sleep.

How do you use a staging site for big updates?

Copy the live site to staging, run the update there, click through the key pages, and only then update the live site.

A staging site is a copy of your site on a private address where you can break things safely. Many hosts offer one-click staging, and the guide to setting up a staging site for WordPress shows the manual route too.

On staging, run the core, plugin and theme updates together, then check the home page, a post, a product or booking page, the contact form and the checkout. If a page breaks, you know which update caused it before any visitor sees it.

Push the staging copy live only after every check passes, or repeat the same updates on the live site by hand. Either way, take a fresh backup of the live site first.

How do you update PHP as part of the job?

Check your PHP version in Site Health, pick a version with security support left, and switch it in your hosting panel.

PHP 8.2 gets security fixes only until 31 December 2026, PHP 8.3 until 31 December 2027, PHP 8.4 until 31 December 2028 and PHP 8.5 until 31 December 2029, as listed on PHP's supported versions page (checked November 2026).

Each branch gets two years of active support, then two years of security fixes only, and then it reaches end of life.

WordPress 7.1 supports PHP 7.4 through 8.5, but WordPress itself recommends PHP 8.3 or newer, as listed on WordPress.org's requirements page. WooCommerce 10.8 and later needs PHP 8.3 or newer and WordPress 6.9 or newer, according to WooCommerce's update documentation.

Switch PHP on staging first, or pick a quiet hour on the live site. The guide to updating the PHP version in WordPress covers the steps and the rollback plan if a plugin fails on the new version.

ItemSafe version in November 2026Where to check
WordPress core7.1.5Dashboard, then Updates
PHP8.3, 8.4 or 8.5Tools, then Site Health, then Info
MySQL or MariaDBMySQL 8.4 or MariaDB 10.11Tools, then Site Health, then Info
WooCommerce10.8 or newerWooCommerce, then Status

What do you do if an update breaks the site?

Stay calm, find which update caused it, restore the backup or roll back that one item, and then fix the cause on staging.

First, check whether the site shows an error or a white screen, and read the message. A white screen after a plugin update usually points at that plugin, and the guide to fixing a site broken after a WordPress update lists the first checks to run.

If you cannot reach wp-admin, rename the last updated plugin folder through your host's file manager or FTP, which turns that plugin off. Then log in, restore the backup if the damage is wide, or reinstall the previous version of the one plugin that broke.

Do not run more updates until the cause is clear. Fix the problem on staging, with the same plugin versions as the live site, and only then repeat the update on the live site.

How often should you update?

Check for updates weekly, apply security releases the day they appear, and review major releases within two weeks.

Minor security releases such as 7.1.5 should go in at once, since they fix flaws that are already public. Plugin security updates deserve the same speed, especially for plugins with many installs. The next major release, WordPress 7.2, is planned for 8 December 2026, as announced on WordPress News.

Set a weekly time to open Dashboard, then Updates, and clear the list. A weekly habit keeps the update list short, and a short list is easy to check one item at a time. Sites that wait months face a long list where one bad update is hard to trace.

Frequently asked questions

What is the latest WordPress version?

WordPress 7.1.5 is the current release, published on 18 November 2026 as a security release. WordPress recommends that sites update to it at once. The next major release, 7.2, is planned for 8 December 2026. Check your version under Dashboard, then Updates.

Does WordPress update itself automatically?

Yes, for minor core releases and translation files, which update by themselves by default. Plugin and theme auto-updates are opt-in since WordPress 5.5, and you turn them on per plugin or per theme. Keep auto-updates off for payment and store plugins, which need a staging check first.

Which PHP version should my WordPress site run?

PHP 8.2 gets security fixes only until 31 December 2026, PHP 8.3 until 31 December 2027, PHP 8.4 until 31 December 2028 and PHP 8.5 until 31 December 2029. WordPress recommends PHP 8.3 or newer. Switch PHP on staging first, or pick a quiet hour on the live site.

How do I back up WordPress before an update?

Take a full backup of files and database, download a copy off the server, and check the backup file is not empty. Test a restore at least once on a staging copy before you need it for real. A backup you have never restored is a guess, not a safety net.

What should I do if a WordPress update breaks my site?

Find which update caused it, then restore the backup or roll back that one item. If you cannot reach wp-admin, rename the last updated plugin folder through your host's file manager, which turns that plugin off. Then log in, fix the cause on staging, and repeat the update on the live site.

Sources

  1. WordPress 7.1.5 Release WordPress.org
  2. Dashboard Updates screen WordPress.org
  3. Plugin and themes auto-updates WordPress.org
  4. Managing Updates Learn WordPress
  5. Supported Versions PHP
  6. Update PHP and WordPress WooCommerce
  7. Requirements WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.