Takeaway: On November 18, 2026, WordPress.org released WordPress 7.1.5 as a core security update that fixes 20 issues. The project recommends updating sites immediately, either from Dashboard → Updates or by downloading the release from WordPress.org. Sites that already allow automatic background updates should receive the package without a manual click. This is a later, broader release than WordPress 7.1.4, which addressed a separate upgrade-race issue in October.
The details below come from that official news post, the WordPress 7.1.5 documentation, and the release archive. WordPress.org did not publish CVE identifiers for these issues, and we are not inventing any. The descriptions here use the project’s own wording for each issue class and do not include reproduction steps.
How 7.1.5 differs from the 7.1.4 upgrade-race fix
WordPress 7.1.4 was released on October 28, 2026, according to the official release archive. Our earlier coverage of that version focused on an upgrade-race remote code execution issue and the attack activity reported around it. WordPress 7.1.5 is a new short-cycle security release, dated November 18, 2026. It is not a restatement of the 7.1.4 fix.
Among the 20 items in 7.1.5 is a separate issue that WordPress.org describes as “unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution,” reported by Logan Homolka. That is official language for a different bug class than the earlier upgrade-race report. Site owners who already moved to 7.1.4 still need 7.1.5, or the matching backport listed for their branch.
What site owners should install
If you run the current 7.1 line, update to WordPress 7.1.5. WordPress.org says you can do that from the Updates screen in the dashboard or from the download site. If automatic background updates are enabled, the update process will begin automatically.
The news post notes that, as a courtesy, the security fixes were backported to all branches still eligible to receive security updates, currently through 4.7, and reminds readers that only the most recent version of WordPress is actively supported. It also said those backports were in progress and would ship as they became ready. The version documentation, also dated November 18, 2026, lists specific patched releases as available. Use that official list, not an unofficial matrix, when you choose a backport:
| Branch | Official documentation |
|---|---|
| 7.1 | Update to 7.1.5. |
| 7.0 through 6.5 | Each of these branches is affected by all 20 issues. Patched releases listed: 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12, and 6.5.15. |
| 6.4 through 6.2 | Affected by 19 of the 20 issues. Patched releases listed: 6.4.15, 6.3.15, and 6.2.16. |
| 6.1 and 6.0 | Affected by 18 of the 20 issues. Patched releases listed: 6.1.17 and 6.0.19. |
| 5.9 | Affected by 17 of the 20 issues. Patched release listed: 5.9.21. |
| 5.8 through 5.6 | Affected by 15 of the 20 issues. Patched releases listed: 5.8.20, 5.7.22, and 5.6.24. |
| 5.5 through 5.1 | Affected by 13 of the 20 issues. Patched releases listed: 5.5.25, 5.4.26, 5.3.28, 5.2.31, and 5.1.29. |
| 5.0 through 4.8 | Affected by 12 of the 20 issues. Patched releases listed: 5.0.32, 4.9.36, and 4.8.35. |
| 4.7 | Affected by 11 of the 20 issues. Patched release listed: 4.7.40. |
| 4.6 and earlier | WordPress.org says these branches no longer receive security updates. |
Hosts and managed platforms may apply these packages for you, but that is not the same as the dashboard already showing 7.1.5 or the matching backport. Confirm the running version after the update. Plugin and theme updates are separate; this release is a core security package. If you maintain a custom site alongside a page builder, keep builder updates on their own schedule as well — for example, the earlier Oxygen 6.2.2 security update is not replaced by 7.1.5.
The 20 issues, in official wording
WordPress.org lists 20 security updates in this release. The grouping below is only for readability. Each item keeps the project’s description and reporter credit.
Privilege escalation and authorization
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
Cross-site scripting
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
SQL injection, information disclosure, and denial of service
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
Hardening changes
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
The official documentation also lists the core files revised in 7.1.5, including components of the REST API, XML-RPC, Customizer, shortcodes, Meta Query, and several block-related files. That file list is a change log, not a guide to testing or exploiting the issues.
Other official notes in this release
WordPress 7.1.5 is a short-cycle release. The next major version is 7.2, currently planned for December 8, 2026. WordPress.org also says WordPress 7.2 RC 2 has been released and contains all applicable fixes.
A separate certificate change is called out in the news post: 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. Site owners who still rely on very old certificate material should treat that as an official compatibility note, not as one of the 20 vulnerability descriptions.
The release was led by Jeremy Felt, Jerry Jones, and Jarda Snajdr, with a longer official contributor list in the news post.
Key facts
| Item | What official sources say |
|---|---|
| Date | November 18, 2026, according to the WordPress.org news post, version documentation, and release archive. |
| Current-branch fix | WordPress 7.1.5. |
| How many issues | 20 security updates, including two items described as hardening. |
| Highest-impact official wording | Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution. |
| Older branches | Courtesy backports through 4.7, with specific patched versions listed in the November 18 documentation. Only the most recent WordPress version is actively supported. 4.6 and earlier no longer receive security updates. |
| CVE IDs | WordPress.org did not list CVE numbers for these issues. |
| Update path | Dashboard → Updates, or a download from WordPress.org. Automatic background updates begin automatically where they are supported. |
| Next major release | WordPress 7.2, currently planned for December 8, 2026. 7.2 RC 2 has also been released with applicable fixes. |
FAQ
What is WordPress 7.1.5?
It is a core security release published on November 18, 2026. WordPress.org says it features fixes for multiple issues — 20 items in the official list — and recommends that you update your sites immediately.
Is this the same as the WordPress 7.1.4 upgrade-race fix?
No. WordPress 7.1.4 was released on October 28, 2026 and is a separate earlier release. WordPress 7.1.5 is a later short-cycle security update with 20 issues of its own, including an unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution. Installing 7.1.4 does not take the place of 7.1.5.
Which version should I update to?
Sites on the 7.1 branch should update to 7.1.5. Older branches that still receive security fixes should use the patched version listed in WordPress.org’s 7.1.5 documentation, from 7.0.9 down through 4.7.40. WordPress.org says 4.6 and earlier no longer receive security updates, and that only the most recent version is actively supported.
Did WordPress publish CVE numbers for these issues?
No. The official news post and version documentation describe the 20 issues in prose and name reporters, but they do not assign or list CVE identifiers. This article does not add any.
Does 7.1.5 include a remote code execution issue?
WordPress.org describes one of the 20 fixes as unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution. That is the project’s wording. It is not the same issue as the earlier 7.1.4 upgrade-race report, and official posts do not provide exploitation details.
Are older WordPress branches patched yet?
The November 18 news post said courtesy backports to eligible branches, currently through 4.7, were in progress and would ship as they became ready. The version documentation, also dated November 18, lists specific releases such as 7.0.9, 6.9.12, and 4.7.40 as released. Check the version running on your site against that official list.
How do I apply the update?
WordPress.org says you can update automatically from Dashboard → Updates, or download the release from the WordPress.org releases page. If the site supports automatic background updates, the update process will begin automatically. Confirm the new version after it completes.
Does this replace plugin or theme security updates?
No. WordPress 7.1.5 is a core release. Plugin and theme updates are separate. A builder or plugin patch, such as Oxygen 6.2.2, still needs to be applied on its own schedule even after the core update.

Leave a Reply
You must be logged in to post a comment.