TL;DR
WordPress 7.1.5 fixes 18 security vulnerabilities and adds two hardening changes. The most serious bug lets an unauthenticated attacker escalate privileges through Template Part block attributes. According to the release notes, that flaw “could lead to remote code execution.”
This WordPress security release patches privilege escalation, SQL injection, cross-site scripting (XSS) and information disclosure bugs in core. Several need no login at all. The release notes do not mention exploitation or a public proof-of-concept, and none has been confirmed.
Why It Matters
Several Bugs Need No Login
Four issues are labeled unauthenticated, so anonymous visitors can trigger them. Besides the Template Part flaw, they include stored XSS through shortcode attributes in comments. Another leaks private taxonomy terms through the REST API search endpoint. A fourth allows denial of service through batched XML-RPC pingbacks.
WordPress Is a Frequent Target
Core bugs reach every site that runs the affected code. In September, WordPress also had to patch a critical unauthenticated path traversal flaw in core, as Wordfence reported. As a result, attackers watch each WordPress security release for fresh targets.
How the Attack Works
The WordPress 7.1.5 release announcement gives only short summaries. Here is how the main groups break down.
Privilege Escalation
Logan Homolka reported the Template Part flaw. Separately, Yuval Miller found a multisite bug that lets a site Administrator take over a Super Admin account through Customizer menu previews.
SQL Injection
Two bugs allow SQL injection. One hits WP_Meta_Query through nested relation values. The other abuses the front page setting in Customizer changeset previews.
Cross-Site Scripting
Eight fixes address XSS. Most need an account, from Contributor up to Administrator. Targets include oEmbed responses, the Comment Date block, media filenames and Openverse image metadata. Also, a reflected XSS sits in the legacy media library popup.
Information Disclosure and Other Bugs
Four bugs leak data. For example, Author-level users could see user email addresses through the REST API comments endpoint. Subscribers could also read comments through XML-RPC wp.getComments. Finally, an authorization bypass let Author-level users edit comments in the admin.
Affected Versions
The fixes ship in WordPress 7.1.5. The release notes do not list affected versions or backports for older branches. Also, no CVE IDs have been published yet.
Patch and Mitigation
Update to WordPress 7.1.5 now. Sites with automatic background updates should receive it without action. Still, admins should confirm the version under Dashboard, then Updates.
- Check multisite networks first, given the Super Admin takeover bug.
- Disable XML-RPC if you do not need it.
- Review comments for suspicious shortcodes.
Looking ahead, WordPress 7.2 is planned for December 8. Until then, WordPress 7.1.5 is the safe version to run.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!