WordPress released 7.1.5 on 18 November 2026, a security release with 20 fixes. It is the eighth core security release since 17 July, and comes three weeks after 7.1.4.
Four That Need No Login
Four of the 20 can be triggered by a visitor who is not logged in:
- Privilege escalation through Template Part block attributes, which the release notes say “could lead to remote code execution”. Reported by Logan Homolka.
- Stored cross-site scripting through shortcode attributes in comments. Reported by Rafie Muhammad of Awesome Motive.
- Denial of service through batched XML-RPC pingbacks. Reported by Giovanni Cintolo.
- Disclosure of private taxonomy terms through the REST API search endpoint. Reported by Anthropic.
The Other Sixteen
The rest need a logged-in account, from Subscriber up to Administrator depending on the issue:
- Two SQL injection flaws, one in
WP_Meta_Querythrough nested relation values, and one through the front page setting in Customizer previews. - A multisite privilege escalation that lets a site Administrator take over a Super Admin account through Customizer menu previews.
- Seven cross-site scripting issues: two in the block editor, and one each in the Customizer, the Comment Date block, oEmbed responses, the Interactivity API and the legacy media library popup.
- Three information disclosures, including user email addresses exposed to Author-level accounts through the REST API comments endpoint.
- An authorisation bypass in comment editing, open to Author-level accounts.
- Two hardening changes. One removes the block editor’s Imgur embed, which was the subject of a cross-site scripting fix in 7.1.3.
WordPress has not yet published severity ratings or CVE numbers for 7.1.5. The GitHub advisories for 7.1.4 appeared the day after release, so ratings for these may follow shortly.
7.1.4, on 28 October
7.1.4 fixed what WordPress counts as 22 vulnerabilities, many of them stored cross-site scripting in the Interactivity API. It also fixed a race condition during core updates that could lead to remote code execution while an update was running. The security team rated that one Low in its GitHub advisory.
Between them, 7.1.4 and 7.1.5 credit Anthropic with four fixes. That brings the core vulnerabilities it has reported since July to ten, across five releases.
WordPress 7.2, the next major release, is planned for 8 December. Its second release candidate, out the same day as 7.1.5, includes these fixes.
What Our Clients Need to Do
Nothing. For most of our clients, 7.1.5 installs automatically through WordPress’s background updates. As with each core security release this year, we check that every site we manage has actually moved to the new version, rather than assuming the update ran.
Sites we keep on an older branch for compatibility get the backport for that branch, and we confirm those the same way.
Self-Managed Sites
Go to Dashboard → Updates and confirm you are on 7.1.5. On the 7.0 branch the equivalent is 7.0.9, and on 6.9 it is 6.9.12. If no update is offered yet, check again in a day or two, as some backports are still shipping.
If you have updated by hand for each of the eight releases since July, check whether core auto-updates are turned off on your site.
For a once-over on whether your site is patched and set up to stay that way, get in touch or see our managed WordPress care plans.