WordPress 7.1.5 shipped on November 18, 2026 as a security release, with 20 fixes listed in the announcement. The project recommends updating immediately. Patched versions of the older branches came out the same day: 7.0.9, 6.9.12, 6.8.13, 6.7.12 and 6.6.12. WordPress 7.2 RC 2 already includes the fixes, and 7.2 is still planned for December 8.
The flaw that calls for speed
The most serious item on the list is an unauthenticated privilege escalation through Template Part block attributes, which according to the announcement "could lead to remote code execution". Unauthenticated means the attacker needs no account on the site.
Three other flaws can be exploited by an anonymous visitor:
- stored XSS through shortcode attributes in comments, meaning a script saved in a comment that runs in the browser of whoever opens the page;
- exposure of private taxonomy terms through the REST API search endpoint;
- denial of service through batched XML-RPC pingbacks.
The rest require some account on the site. There are two SQL injections (one in WP_Meta_Query, another through the front page setting in Customizer changeset previews), a multisite flaw that lets a site administrator take over the Super Admin account, several XSS issues reachable by contributors or authors, and leaks of user emails and comments through the REST API and XML-RPC.
The announcement includes no CVE identifiers or severity scores, and at the time of writing none of the flaws was listed as actively exploited.
Who is in scope
Every self-hosted WordPress. How much risk depends on configuration:
- sites with open comments are exposed to the shortcode XSS without anyone needing an account;
- sites with XML-RPC enabled are exposed to the pingback denial of service;
- multisite networks with site administrators who are not fully trusted are exposed to the Super Admin takeover;
- portals with many external authors and contributors, such as newsrooms and corporate sites where several departments publish, accumulate the flaws that require an account.
Managed hosts usually apply security releases themselves, but it is worth checking the dashboard instead of assuming. Two weeks ago, WordPress 7.1.4 fixed a flaw that CISA confirmed was being exploited; anyone who updated by hand then will repeat the process now.
What to do and by when
Update to 7.1.5, or to the patched version of the branch in use, this week. Sites with automatic background updates get the version on their own; confirm on the updates screen or with wp core version that it was applied.
Where updates are manual, the practical question is who does it on each site. In agency portfolios and in sites delivered and then forgotten, the answer is often nobody, which is the problem discussed in who looks after the system once the project ends.
Until the update goes out, turning off XML-RPC where it is not used and closing anonymous comments reduce exposure to two of the unauthenticated flaws. That does not cover the Template Part flaw, which only the update fixes.
What is still unknown
The announcement says the fixes are being backported to every branch that receives security updates, back to 4.7, and that those packages "will ship as they become ready". On the date of this article, the releases page listed branches 7.0 to 6.6 as patched. Anyone on 6.5 or earlier needs to watch the releases page; the safer option is moving to the current branch, since only the latest version is actively supported.
There are also no public technical details yet about the Template Part flaw, nor information on which versions it affects.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.