WordPress released version 7.1.5 on November 18, 2026, fixing 20 security issues in core. One lets an unauthenticated attacker escalate privileges through Template Part block attributes, a path that could lead to remote code execution.
At a Glance
- WordPress 7.1.5 fixes 20 core security issues, and the project tells site owners to update immediately.
- Yuval Miller reported a Multisite flaw that let a site Administrator take over a Super Admin account through Customizer menu previews.
- Christiaan Swiers and Rudy Faile reported separate SQL injection bugs in WP_Meta_Query and in Customizer changeset previews.
- WordPress is backporting the fixes to branches as old as 4.7, while installs on 4.6 and earlier get no security updates.
Template Part bug needs no account
Logan Homolka reported the flaw in the Template Part block, which WordPress uses for shared layout pieces like headers and footers. The release announcement gives no exploit details. It also doesn’t say which site configurations would let the bug reach code execution, or mention any attacks using it.
Other entries on the list also work without a login. Rafie Muhammad of Awesome Motive found stored cross-site scripting (XSS) via shortcode attributes in comments, and Giovanni Cintolo’s denial-of-service bug abuses batched XML-RPC pingbacks.
AI developer Anthropic reported a REST API search bug that exposed private taxonomy terms, such as categories and tags, to logged-out visitors. Its second credit is a reflected XSS in the legacy media library popup.
The two SQL injection entries carry no role label, so the list doesn’t say who can trigger them. Christiaan Swiers’s bug abuses nested relation values in WP_Meta_Query, which builds database queries from metadata. Rudy Faile’s runs through the front page setting in Customizer changeset previews. Neither overlaps with the export issue fixed in 7.1.3.
WordPress 7.1.5 is a security release with fixes for multiple issues. Update your sites immediately from the WordPress Dashboard. If a site supports automatic background updates, the process will begin automatically. https://t.co/0NkayX4F3u
— WordPress (@WordPress) November 18, 2026
Account roles decide each site’s exposure
Several fixes name the lowest account role an attacker needs, and that shifts the risk from site to site. A Subscriber+ leak through XML-RPC’s wp.getComments matters for any site with open sign-ups or a membership area. Contributor+ accounts could plant stored XSS through the Comment Date block’s date format or through media filenames in the block editor. Author+ accounts could pull user email addresses from the REST API comments endpoint or bypass authorization when editing comments.
Multi-author publications hand out Contributor and Author accounts by design, which puts these bugs inside their normal workflow. Yuval Miller’s Multisite bug reaches higher still, since a Super Admin manages the entire network.
The announcement carries no CVE IDs or severity ratings, so admins have no common score to rank the fixes against. Two entries are hardening changes: one tightens JSON media type matching, and one removes the block editor’s Imgur embed variation, whose provider is gone.
Older branches get fixes as backports land
WordPress’s backports to older branches are still in progress, and the announcement says they “will ship as they become ready.” The 7.1.5 documentation lists 7.0.9, 6.9.12 and 4.7.40 among the patched releases. According to SecNews, the same documentation shows branches 7.0 through 6.5 exposed to every issue on the list, while 4.7 faces 11. Admins on older lines should confirm their build is actually available before assuming they’re covered.
The 6.9.12 release and older builds also drop 1024-bit certificates from the bundled root certificates, matching a change WordPress made in 7.0. The project still says only the newest version gets active support. WordPress version usage data shows how the install base splits across major versions, which is why the backport queue matters.
Open Questions
Two questions stay open: which site setups let the Template Part bug reach code execution, and when each older-branch build ships. Neither changes the immediate call. An unauthenticated route toward code execution, with no severity scores to sort by, makes this a patch-now release on every branch still receiving fixes.
Admins can install it from Dashboard, then Updates, then Update Now, and should confirm the version number afterward. Sites that support automatic background updates start the process on their own, though the same check still applies. WordPress 7.2 Release Candidate 2 already carries the applicable fixes, and the final 7.2 release is currently planned for December 8.




















































