WordPress released version 7.1.5 on November 18 and is telling site owners to update immediately. The security release fixes 20 vulnerabilities, and the most serious, an unauthenticated privilege escalation through Template Part block attributes, could lead to remote code execution, according to the project's official release notes. Unauthenticated means an attacker would not need an account on the site.
Hong Kong's HKCERT relayed the release in a bulletin on November 19. Neither WordPress nor HKCERT lists CVE identifiers or CVSS scores for the fixes, so severity has to be read from the descriptions.
Four of the bugs need no login at all
The release notes describe each fix in one line and credit the reporter. The ones an outsider could reach without signing in are the most pressing:
- Privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- Stored cross-site scripting via shortcode attributes in comments, reported by Rafie Muhammad of Awesome Motive. Cross-site scripting lets an attacker plant script that runs in other visitors' or admins' browsers.
- Denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Disclosure of private taxonomy terms through the REST API search endpoint, reported by Anthropic.
The rest require some level of access, from Subscriber up to Administrator. They include two SQL injection bugs (one in WP_Meta_Query via nested relation values, one via the front page setting in Customizer changeset previews), a multisite flaw that lets a site Administrator take over a Super Admin account through Customizer menu previews, several stored XSS issues reachable by Contributors, and information leaks that exposed user email addresses to Authors. Two items are hardening changes rather than vulnerabilities.
Patched versions reach back to WordPress 4.7
WordPress backported the fixes to every older branch it still maintains as a courtesy. HKCERT lists the fixed builds, among them 7.0.9, 6.9.12, 6.8.13, 6.7.12 and 4.7.40. WordPress 4.6 and earlier receive no security updates.
WordPress core fixes tend to draw attackers quickly; our coverage of the 7.1.4 update-window flaw showed how fast exploitation can follow a release.
Update to 7.1.5 now, or the fixed build for your branch
- Sites with automatic background updates enabled should receive the release on their own. Confirm the version under Dashboard, Updates.
- Sites pinned to an older branch should move to that branch's fixed build, and plan an upgrade to 7.1.x, since only the latest version is actively supported.
- Multisite networks should prioritize the update because of the Super Admin takeover bug.
None of the 20 fixes is reported as exploited, but one-line release notes are a map as well as a warning, and the unauthenticated bugs are the ones worth closing before someone else reads them closely.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.