Vulnerability
WordPress 7.1.5 was released on November 18, 2026, as a security release. It fixes 19 security issues and makes one hardening change in WordPress core. The WordPress project recommends updating immediately.
Fixes have also been released for every older branch that still receives security updates, back to WordPress 4.7.
The most serious issue is an unauthenticated privilege escalation through Template Part block attributes. The WordPress project states it could lead to remote code execution.
The release also fixes two SQL injection flaws, several cross-site scripting (XSS) flaws and an unauthenticated denial of service in XML-RPC pingbacks. It fixes a multisite flaw that lets a site Administrator take over a Super Admin account, and several information disclosure and authorization issues.
CVE and severity
No CVE identifiers had been assigned and no CVSS scores had been published as of November 19, 2026. The WordPress project lists the issues without severity ratings.
Impact
Four of the issues can be exploited without an account:
- Privilege escalation through Template Part block attributes, which could lead to remote code execution.
- Stored XSS through shortcode attributes in comments.
- Denial of service through batched XML-RPC pingbacks.
- Disclosure of private taxonomy terms through the REST API search endpoint.
The rest require an account:
- SQL injection in
WP_Meta_Querythrough nested relation values, and SQL injection through the front page setting in Customizer changeset previews. - Multisite privilege escalation that lets a site Administrator take over a Super Admin account through Customizer menu previews.
- Stored XSS for Contributor and above through oEmbed provider responses, the Comment Date block date format and media filenames converted to a File block. Administrators can also store XSS through Customizer previews.
- Reflected XSS in the legacy media library popup, and XSS in
wp_interactivity_data_wp_context()and through Openverse image metadata in the block editor. - Authorization bypass for Author and above through comment editing in the admin.
- Disclosure of user email addresses through the REST API comments endpoint, for Author and above.
- Disclosure of post and template author assignment through the REST API, for Editor and above.
- Information disclosure through XML-RPC
wp.getComments, for Subscriber and above.
The hardening change tightens a malformed regular expression that broadened JSON media type matching. It also removes the block editor’s Imgur embed variation, whose server-side provider no longer exists.
Exploit status
As of November 19, 2026, public reporting doesn’t indicate exploitation in the wild. None of the issues are listed in the CISA Known Exploited Vulnerabilities catalog.
Given the number of unauthenticated issues and how widely WordPress is deployed, update sites promptly and confirm that automatic background updates have applied.
Affected component and versions
The issues affect WordPress core. 7.1.5 is the fixed release for the 7.1 branch, so treat earlier 7.1.x releases as affected.
The WordPress project states that every supported branch is affected by most of the issues, and fixes are available as security releases for older branches. No per-version breakdown has been published.
WordPress 4.6 and earlier no longer receive security updates and can’t be patched through an official release.
Fix and mitigation
- Update to the fixed release for the branch in use: 7.1.5, 7.0.9, 6.9.12, or the corresponding security release for older branches back to 4.7.
- WordPress only actively supports the most recent version, so moving to the latest release is preferred over staying on an older branch.
- Sites on 4.6 or earlier have no official patch and should be upgraded to a supported branch.
- Confirm that automatic background updates have applied.