WordPress shipped three simultaneous security releases on November 18, 2026: 7.1.5 for the current branch, plus 7.0.9 and 6.9.12 for earlier ones. In total, twenty fixes close issues ranging from minor information disclosure to an unauthenticated privilege escalation capable of leading to remote code execution. No CVE identifiers accompany this release, as WordPress continues to document its advisories by description rather than external reference.
The most serious flaw: Template Part block attributes
Reported by researcher Logan Homolka, this vulnerability allows unauthenticated privilege escalation through the editor’s Template Part block attributes, with a documented path to remote code execution. It’s the only one of the twenty fixes to combine both qualifiers, making it the update priority for any site using the block editor — which is to say, nearly every modern install.
The rest of the batch: XSS, SQL and information leaks
The remaining fixes cover very different profiles: a SQL injection in WP_Meta_Query via nested relation values, another in Customizer changeset previews, several stored XSS issues triggered by Contributor or Author roles (media file names, shortcode attributes in comments, Openverse metadata), and information leaks via the REST API and XML-RPC — including one that exposed authors’ email addresses through the comments REST endpoint, fixed at the request of Ben Bidner.
| Version | Branch | Fixes | Scope |
|---|---|---|---|
| 7.1.5 | 7.1.x (current) | 20 | All listed flaws |
| 7.0.9 | 7.0.x | Backport | Applicable subset |
| 6.9.12 | 6.9.x | Backport | Applicable subset |
Updating
Sites configured for automatic minor updates receive 7.1.5 without any action. Everyone else should force the update from the dashboard, or on the command line:
wp core update --minor
wp core verify-checksumsOnly one of the twenty flaws combines unauthenticated privilege escalation with a path to code execution: that’s the one that should trigger the update, not the full list.
Two of the fixes — the JSON media-type validation hardening and the removal of the now-defunct Imgur embed variant — are preventive hardening, not responses to an ongoing incident. That changes nothing about priority: 7.1.5 should be applied as a whole, not fix by fix.
The pace of these security releases matches what was already observed with Node.js in November and with WordPress plugins themselves, as detailed in the alert on two widely used plugins back in September. For self-hosted sites, the settings recommended in the WordPress self-hosting guide already cover disabling XML-RPC, a recurring target among the fixes shipped here.
Key takeaways
WordPress 7.1.5, 7.0.9 and 6.9.12 fix twenty flaws on November 18, 2026. Only one, the Template Part block’s unauthenticated privilege escalation, justifies an immediate update rather than waiting for the next maintenance window.
Twenty fixes in a single changelog is the format that pushes people toward collective underestimation: you read the number, assume most of them are minor, and put it off. The right reading is the opposite one — find the line that combines severity with ease of exploitation, treat that one as an isolated emergency, and let the rest follow as background work. — Simon Janvier
Further reading: the official WordPress 7.1.5 changelog.
