WordPress 7.1.5 security update fixes many XSS and SQL flaws
WordPress.org published 7.1.5 as a security release that addresses multiple XSS, SQL injection, information disclosure, and privilege escalation issues. WordPress.org says to update your sites immediately.
WordPress.org has released version 7.1.5 as a security update that fixes a long list of vulnerabilities. Because this is a security release, WordPress.org recommends you "update your sites immediately." You can install the update from your WordPress Dashboard, download it from WordPress.org, or let automatic background updates run where supported.
What WordPress.org changed
According to WordPress.org, 7.1.5 is a short-cycle security release that addresses multiple classes of issues reported by the WordPress Security Team and outside researchers. The release notes list fixes that include reflected and stored cross-site scripting, SQL injection, privilege escalation, unauthenticated information disclosure, and an unauthenticated denial of service. WordPress.org also says the release includes a hardening change that removes the block editor's Imgur embed variation because its server-side provider is no longer available.
WordPress.org notes the release was led by Jeremy Felt, Jerry Jones, and Jarda Snajdr, and it thanks a long list of contributors and reporters from both the Security Team and external organizations for the findings.
Why this matters for your sites
The set of fixes covers multiple attack paths that affect different user roles and features. The release notes list issues that could allow an Administrator to escalate to Super Admin in multisite via Customizer previews, allow unauthenticated endpoints to disclose private taxonomy terms, expose author emails through the REST API comments endpoint, and permit SQL injection through nested relation values in WP_Meta_Query. Other entries name reflected XSS in the legacy media popup, contributor and author level XSS via comment fields and media filenames, and an unauthenticated denial of service via batched XML-RPC pingbacks.
Because the problems touch the REST API, XML-RPC, Customizer previews, and the block editor, a range of sites and plugins that interact with those systems could be affected. WordPress.org also reports an issue in Template Part block attributes that could lead to remote code execution in some circumstances.
WordPress security update: immediate steps
Follow these steps now, based on the update and installation guidance in the WordPress.org release post:
- Update your site immediately from the Dashboard, using Updates then Update Now, or download 7.1.5 from WordPress.org.
- If you run multiple sites, check which sites have automatic background updates enabled and verify those updates completed successfully.
- Review who has Administrator or Super Admin access on multisite installs, since the release addresses a multisite privilege escalation vector.
- Confirm plugins and themes that touch the REST API, XML-RPC, the Customizer, or the block editor are up to date and test critical workflows after updating.
- If you need hands-on help updating, consider professional assistance: Running WordPress or Formidable Forms? Get help from a Formidable Masterminds developer.
Additional release details and rollout
WordPress.org says the security fixes were backported to all branches eligible to receive security fixes, currently through 4.7, and that those backports are in progress and will ship as they become ready. The release notes also call out that in WordPress 7.0, 1024 bit certificates were removed from bundled root certificates, and that change has been applied to 6.9.12 and earlier as part of this release.
The post also notes WordPress 7.2 RC2 is available and contains all applicable fixes from 7.1.5.
If you cannot update right away
WordPress.org's guidance is to update immediately, but if you must delay, take these interim measures:
- Limit access to administrative accounts and reduce the number of users with high privileges where possible.
- Temporarily disable XML-RPC if your site does not need it, since the release lists an unauthenticated denial of service via batched XML-RPC pingbacks.
- Monitor logs and intrusion detection alerts for unusual REST API or Customizer preview activity.
- Plan a maintenance window to apply the update as soon as possible and test the site in a staging environment before pushing it to production.
If you want more detail on the specific fixes and the reporters credited for each finding, see the official release post on WordPress.org, which lists the full set of issues and contributors.
Sources
- WordPress 7.1.5 Release WordPress.org
This post was drafted with AI from the reporting linked above and published by The Jones Foundry. For full details, read the original sources.