Why the release matters

WordPress released version 7.1.5 on 18 November 2026 and described it as a security release. The release notes list fixes for several security issues. WordPress recommends that site owners update their sites.

The update applies to WordPress core. It does not update every plugin, theme, server package or custom component on a site. Review each part of the stack and use the release notes for version-specific details.

Update with a recovery plan

Before a change, confirm that a recent backup exists and that you know how to restore it. Update a staging copy first when the site has complex integrations or custom code. Then update production during a suitable maintenance window and check the front end, dashboard, forms and checkout flows.

If you manage many sites, confirm the result for each domain. A dashboard may report one site as current while another copy, subsite or staging environment remains behind. Record the installed version and who verified it.

Check the rest of the WordPress stack

Review plugin and theme updates, remove components that are no longer used, and confirm that administrator accounts still need their access. Check the hosting control panel, PHP version, database backups and access credentials as part of the same maintenance cycle.

A core update does not prove that a site is free from compromise. If you see unexpected users, redirects or files, preserve evidence and investigate before treating the update as a clean-up. A WordPress security audit can review the site and its hosting controls.