WordPress 7.1.5 came out on 18 November 2026. It is a security release, and WordPress recommends updating straight away. It fixes 20 issues, according to the security company Patchstack, including one that WordPress says could lead to running code on the server.
Here is what changed, who is at risk, and a short checklist for your site.
Do I need to do anything?
Probably very little, but check. Most WordPress sites install security releases on their own. Log in and look at Dashboard → Updates:
- If it says you have WordPress 7.1.5, you’re done with the update.
- If not, update now. Take a backup first if you don’t have a recent one.
Older versions got fixes too. Every branch back to WordPress 4.7 received a patched release. Versions 4.6 and older get no security updates at all, so a site that old should be moved to a current version.
What 7.1.5 fixes
Patchstack’s summary groups the fixes like this:
- Running code on the server: a crafted Template Part block could lead to code running on the server. Someone with editor access has to open the crafted content.
- Taking over a network: on a multisite, a site administrator could become a Super Admin through Customizer menu previews.
- Database attacks (SQL injection): three issues, one of them reachable without logging in.
- Scripts injected into pages (XSS): several, in comments, the Comment Date block, embeds, media file names and the old media pop-up.
- Information leaks: private taxonomy terms, user emails, commenter emails and IP addresses could be exposed in some cases.
- Slowing a site down: batched XML-RPC pingbacks could be used to overload a site.
Several of these need a logged-in user, such as a contributor or editor. That’s why the user checklist below matters as much as the update.
A short security checklist
- Update WordPress to 7.1.5 (or the patched release of your branch).
- Update plugins and themes too. Most real attacks use outdated plugins, not WordPress itself.
- Review your users. Remove accounts that no longer need access, and lower roles where you can. A guest writer usually needs Contributor, not Editor.
- On multisite, also review the list of site administrators.
- Check PHP. Your host’s PHP version also gets security fixes. Ask your host if you’re not sure you’re on a supported version.
- Keep a recent backup somewhere other than your hosting account.
Should I turn on automatic updates?
For minor and security releases, yes. They are small and well tested, and the risk of waiting is usually higher than the risk of updating. WordPress turns them on by default. If a developer switched them off, ask why.
Major versions (such as the coming 7.2) are different: test them on a copy of the site first if you have custom code or many plugins.
How the Arva SEO plugin helps
The free Arva SEO WordPress plugin includes a security scanner that checks your WordPress version, plugins and PHP against known problems and shows what needs you on the WordPress Dashboard. From version 2.19.0 it can also keep a weekly backup of your site on Arva SEO’s servers, on every plan, so you have a copy to restore if an update goes wrong.
See the free WordPress security scanner for details.
Sources: WordPress News, Releases; Patchstack, WordPress 7.1.5 security release.
Facts checked: 19 November 2026.