Update WordPress to the current release on WordPress

Why it matters

WordPress.org itself lists the WordPress version this site shows as insecure, so it misses security fixes that are already published. Updating closes those holes; the newest release of your line is the smallest step, the current release the best one.

Staged change. Do this in stages and check each one before the next, so a mistake does not break your site or your mail.

The fix

1. Back up the site, then open Dashboard, Updates and update WordPress. If the current release is a big jump, first update to the newest release of your line with wp core update --version=<that version>, then to the current one.
2. Update every plugin and theme, remove those you do not use, and check the main pages of the site.
3. Make sure minor and security updates install automatically. Remove a define('WP_AUTO_UPDATE_CORE', false) or define('AUTOMATIC_UPDATER_DISABLED', true) line from wp-config.php if there is one.

wp core version
wp core update
wp plugin update --all
wp theme update --all

Read the documentation ↗(opens in a new tab)

Related

• Reported by the cms and framework advisories check
• Keep the software named in the finding up to date
• Update the CMS or application to a patched release
• Patch the exploited vulnerability in your CMS or application
• Move off end-of-life software