WordPress 7.1.5 shipped on November 18, 2026, as a short-cycle security release patching 18 vulnerabilities across core, four of which require no login at all. The most serious is a privilege escalation bug in the Template Part block that WordPress’s own release notes say “could lead to remote code execution.” The fixes were backported all the way to version 4.7, and the WordPress.org release post tells site owners to update immediately.
What WordPress 7.1.5 Actually Fixes
Per the official WordPress 7.1.5 release announcement, four of the patched issues don’t require an account on the site at all:
- Information disclosure of private taxonomy terms through the REST API search endpoint (reported by Anthropic)
- Stored XSS via shortcode attributes in comments (reported by Rafie Muhammad of Awesome Motive)
- Denial of service via batched XML-RPC pingbacks (reported by Giovanni Cintolo)
- Privilege escalation via Template Part block attributes, which WordPress says could lead to remote code execution (reported by Logan Homolka)
The release also closes ten authenticated issues that need at least a Subscriber, Contributor, Author, Editor, or Administrator account, plus four more where the required privilege level wasn’t specified. That list includes a SQL injection in WP_Meta_Query, a stored XSS in the Comment Date block, and a Customizer flaw that lets a Site Administrator on a multisite network take over the Super Admin account. None of it is theoretical: this is the kind of chain that turns a low-privilege account, a contributor login, or an open comment form into a foothold.
Who Needs to Act, and How Fast
No CVE had been publicly assigned to the Template Part issue as of this writing, and WordPress hasn’t reported exploitation in the wild yet. That’s not a reason to wait. The fact that the fix was backported as far back as 4.7 signals how broadly the underlying code path exists, and the unauthenticated nature of the worst bug means a scanner doesn’t need a valid login to find it.
Sites with automatic background updates turned on should already be on 7.1.5. Everyone else, especially agencies managing client sites where auto-updates are disabled for stability reasons, should check their version number in the dashboard today rather than waiting for the next scheduled maintenance window.
Why the Template Part Bug Is the One to Watch
Template Part blocks pull content into a theme’s header, footer, or other reusable regions, and they’re exposed to anyone who can submit block attributes, which on many sites means anonymous visitors through forms, comments, or REST endpoints. A flaw that lets an unauthenticated request manipulate those attributes and reach remote code execution is a different category of risk from an XSS bug that needs a victim to click something. It’s the same shape of problem that made the WordPress 7.1.4 core-update race condition and last year’s wp2shell chain so disruptive: no credentials needed, and the clock starts the moment the patch is public and researchers start reverse-engineering it.
This also lands three weeks ahead of WordPress 7.2, which is scheduled for December 8, 2026, so sites should expect another update cycle shortly after this one. For a rundown of how the previous core security release played out, see our coverage of WordPress 7.1.4 patching 22 flaws while attackers raced to exploit the core update window.
For agencies or site owners who don’t have a process for confirming every client site is actually patched within days of a core security release, rather than whenever someone happens to log in, that gap is usually where these bugs do damage. A WordPress Development partner that tracks security releases as part of ongoing maintenance closes that gap before it becomes an incident.

