← All security briefings

Attention

WordPress 7.1.5 security release: 20 listed security and hardening items, Template Part escalation now confirmed by a vendor advisory

Identifiers: WordPress-7.1.5-security-release · GHSA-pmp8-6cv8-q323

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

On 18 November 2026 the WordPress project released 7.1.5 as a security release. The release post and HelpHub list 20 security and hardening items. That is 20 entries on one list, not 20 separate CVEs. The items include a template-related privilege escalation, two SQL injection fixes, a multisite privilege escalation, several cross-site scripting and data disclosure fixes, and denial-of-service fixes. The earlier version of this briefing already confirmed the 7.1.5 release. Since then the Template Part escalation has received a published vendor advisory, GHSA-pmp8-6cv8-q323, which corroborates the release notes. The advisory lists WordPress 7.1.0 through 7.1.4 as affected and 7.1.5 as fixed, and states that the fix for this particular issue was backported to older branches back to 5.9, for example 7.0.9, 6.9.12 and 5.9.21. The general release archive now confirms 18 November security builds for older branches, including 4.7.40, which the earlier briefing had not yet confirmed. Do not read the archive as meaning every fix reached every older branch, or that the Template Part issue exists on 4.7. WordPress asks site owners to update immediately.

Classification reason: Attention. A fixed stable release is available and WordPress asks site owners to update immediately. The release bundles multiple security fixes, including a privilege escalation that the vendor advisory says could lead to unauthorized administrative access and code execution. The opened primary notices do not establish exploitation in the wild.

Impact

The vendor advisory describes the Template Part issue as a privilege escalation that could lead to unauthorized administrative access and code execution on the site. The conditions matter. An account with the Author role or higher and access to the relevant content can place affected block content, but the vulnerable editor activity happens in an Administrator's session. Separately, an unauthenticated person could try to induce a signed-in Administrator to follow a crafted link. An Author account does not gain elevated privileges on its own. The other items in the release cover SQL injection, multisite escalation, cross-site scripting, data disclosure and denial of service. For a small business, a successful attack on any of these could expose customer or order data, alter pages, create rogue administrator accounts, or take the site offline.

Who is affected

Applies to any self-hosted or managed WordPress site running 7.1.0 through 7.1.4. Sites on older branches are also in scope. The Template Part fix was backported down to 5.9, and the archive lists 18 November security builds for other older lines such as 4.7.40. Those older builds are courtesy releases and do not establish ongoing support for those branches. Managed hosts and sites with automatic core updates may already be on 7.1.5. Confirm rather than assume. The release candidate line is not a production recommendation. In production, prefer the stable 7.1.5 build and check the current official guidance on supported updates and branches.

Products and versions

Products and versionsAffectedFixed
WordPress core (November 18 release set) Item-specific; not all fixes apply to all older branches 7.1.5; older branch courtesy releases listed by the project through 4.7
WordPress Template Part block 7.1.0–7.1.4 and enumerated branches 5.9 through 7.0 in GHSA-pmp8-6cv8-q323 7.1.5, 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12, 6.5.15, 6.4.15, 6.3.15, 6.2.16, 6.1.17, 6.0.19, 5.9.21

Exploitation evidence

Exploitation not established. As of 20 November 2026 the opened primary notices from the WordPress project and the GHSA advisory do not establish exploitation in the wild. The Template Part issue requires either an Author or higher account with access to the relevant content, with the vulnerable editor activity occurring in an Administrator's session, or an unauthenticated person inducing a signed-in Administrator to follow a crafted link.

Sources: WordPress project, WordPress project

Actions

  1. Log in to the WordPress admin dashboard and confirm the exact installed core version.
  2. If the site runs 7.1.0 through 7.1.4, update to the stable 7.1.5 release through the normal update screen or your host's update mechanism.
  3. If the site runs an older branch, apply the matching 18 November security build for that branch as an interim step, then plan a move to a currently supported branch. The official release archive shows which build applies to your line.
  4. Take a full backup of files and database before updating and confirm you can restore it. Use a staging site first where one exists, without delaying a critical security fix.
  5. After updating, check the site front end, checkout or contact forms, media uploads, and the block and template editors.
  6. Review the accounts holding Author, Editor and Administrator roles. Disable or deprovision access that is no longer needed through your existing user management process, and confirm the remaining accounts belong to known people.
  7. Remind Administrators to be cautious with unexpected links while signed in to the site.
  8. On multisite installations, the network administrator should confirm the update across the whole network, not just the main site.

Unknowns

  • The primary release notices and HelpHub do not state a CVE identifier for every one of the 20 items.
  • Only the Template Part issue has a confirmed backport list in the opened advisory. Which of the other fixes reached which older branch is not fully documented in the material reviewed.
  • Whether a given managed host has already applied 7.1.5 varies by provider and is not knowable from the release notes.
  • No exploitation in the wild is established in the primary notices opened for this briefing. That is not proof it is not happening.

Sources

  • WordPress project · retrieved https://wordpress.org/news/2026/11/wordpress-7-1-5-release/
  • WordPress project · retrieved https://wordpress.org/documentation/wordpress-version/version-7-1-5/
  • WordPress project · retrieved https://wordpress.org/download/releases/
  • WordPress project · retrieved https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-pmp8-6cv8-q323

Change history

  1. — Published: 19 November 2026: Published briefing and owner checklist for WordPress 7.1.5, the short-cycle security release the WordPress project announced on 18 November 2026 listing 20 security and hardening items. Exploitation status recorded as not established.
  2. — Updated: 20 November 2026: Material update. The earlier briefing already confirmed the 18 November 2026 release of WordPress 7.1.5. This update corrects the description to 20 listed security and hardening items, adds the now-published vendor advisory GHSA-pmp8-6cv8-q323 for the Template Part escalation with its affected range 7.1.0 to 7.1.4 and backports through 5.9, clarifies that the vulnerable editor activity requires Administrator context, confirms the 18 November older-branch courtesy builds such as 4.7.40 that were previously unconfirmed and do not imply every fix on every branch or ongoing support, and notes that WordPress asks owners to update immediately. Status attention.

Subscribe: RSS feed · JSON Feed · Feed format and fields