Security Alert: Update to WordPress 7.1.5 Now

Last updated: 19 November 2026.
On 18 November 2026, WordPress released version 7.1.5, a security release that fixes 20 security issues in WordPress core. The WordPress team's advice is clear: "Because this is a security release, it is recommended that you update your sites immediately."
If you run a WordPress site, this applies to you, whichever version you are on.
Who needs to act
- You have a WordPress maintenance agreement with NetOz: you do not need to do anything. See Maintenance agreement customers below.
- Everyone else, including NetOz hosting customers without a maintenance agreement: please update urgently using the steps below. Your hosting keeps the server patched, but updating WordPress itself is up to you.
- You are not sure whether you have a maintenance agreement: contact us and we will check for you.
Why this update matters
Several of the 20 issues can be exploited without logging in, which means anyone on the internet can try them against your site:
- Privilege escalation that could lead to remote code execution, through Template Part block attributes. This is the most serious fix in the release.
- Stored cross-site scripting (XSS) through comments, using shortcode attributes. An attacker could plant a script that runs when you or your visitors view the comment.
- Denial of service through batched XML-RPC pingbacks.
- Disclosure of private taxonomy terms through the REST API search endpoint.
Other fixes cover issues that need a user account, which matters if your site has contributors, authors, customers or members who can log in:
- SQL injection in meta queries and in Customizer previews.
- Stored XSS that contributors or authors could trigger through oEmbed responses, media filenames, the Comment Date block and Customizer previews.
- Privilege escalation on multisite, where a site administrator could take over a Super Admin account.
- Information disclosure, including user email addresses and post and template authors through the REST API, and comments through XML-RPC.
The release also removes outdated 1024-bit certificates from the bundled root certificates on older branches, and drops an Imgur embed whose provider no longer exists.
Which version you should be on
If you are on WordPress 7.1, update to 7.1.5. If you are on an older branch, the fixes have been backported, and WordPress lists these fixed versions:
| Your branch | Update to at least |
|---|---|
| 7.1 | 7.1.5 |
| 7.0 | 7.0.9 |
| 6.9 | 6.9.12 |
| 6.8 | 6.8.13 |
| 6.7 | 6.7.12 |
| 6.6 | 6.6.12 |
| 6.5 | 6.5.15 |
| 6.4 | 6.4.15 |
| 6.3 | 6.3.15 |
Branches back to 4.7 also receive fixes. WordPress 4.6 and earlier get no security updates at all, so a site on those versions needs a full upgrade.
Staying on an old branch is safe for now only if it is fully patched. The best option is to move to the latest version, 7.1.5, so you also get fixes that are never backported.
How to update
- Take a backup first, of both the files and the database. Your host's backups count, as long as you know how to restore one.
- Log in to your dashboard and go to Dashboard > Updates.
- Click Update to version 7.1.5 (or Update Now).
- Once it finishes, update your plugins and themes too, then check the site's main pages and any forms or checkout still work.
Sites that have automatic background updates turned on will start updating by themselves. Do not assume it worked: check the version shown at the bottom of Dashboard > Updates or under Tools > Site Health > Info.
If you use WP-CLI:
wp core update
wp core version
Keep the rest of your site patched
Core updates are only part of the picture. Most WordPress compromises come through out-of-date plugins and themes, so this is a good moment to:
- remove plugins and themes you no longer use, rather than just deactivating them;
- update everything that remains;
- check that every administrator account is someone you recognise, and that each one uses a strong password and two-factor authentication.
Maintenance agreement customers
If you have a WordPress maintenance agreement with NetOz, you do not need to do anything.
- We are updating every site covered by a maintenance agreement to 7.1.5, or to the patched version of their branch, with a backup taken first.
- We check each site after the update.
- We will contact you directly if a plugin or theme conflict needs your input.
Need help?
If your site is not covered by a maintenance agreement, we can still help. Get in touch and we can apply this update for you as a one-off, check your site for problems, or set up a maintenance agreement so updates like this are handled for you in future.
References
- WordPress 7.1.5 Security Release (WordPress.org News)
- Version 7.1.5 release notes and fixed versions per branch (WordPress.org)
Update log
- 19 November 2026: First published.
Need a hand with hosting or networking?
NetOz provides VM, managed and email hosting, DNS and colocation from a NextDC Tier IV facility in Adelaide.