Key details

  1. WordPress 7.1.5 released 18 November 2026 with immediate-update guidance.
  2. Patchstack counts eighteen vulnerabilities and two hardening fixes.
  3. Unauthenticated Template Part privilege escalation could lead to remote code execution.
  4. Multisite site Administrator could take over a Super Admin.
  5. Several SQL injection, XSS, disclosure and denial-of-service issues were fixed.
  6. Five fixes involve bundled Gutenberg JavaScript packages per Patchstack.
  7. Backports to security-eligible branches through 4.7 are in progress.
  8. No in-the-wild exploitation was established by cited sources.

What builders should take away

  1. Update to 7.1.5 or the actually available patched backport for your branch, and verify completion.
  2. On multisite, audit unexpected administrator and Super Admin changes.
  3. Check bundled editor JavaScript assets as well as PHP code in custom deployment diffs.
  4. Inspect suspicious Template Part, Customizer and account activity if incident evidence warrants it.
  5. Do not install a WordPress 7.2 release candidate on production as a workaround.

What changed

WordPress released 7.1.5 on 18 November 2026 and urged immediate updates. The official security advisory identifies unauthenticated privilege escalation via Template Part block attributes potentially leading to RCE; multisite site-Administrator takeover of a Super Admin via Customizer menu previews; SQL injection in nested WP_Meta_Query relations and Customizer settings; several XSS, information disclosure, and XML-RPC denial-of-service bugs. Patchstack independently analysed twenty fixes, eighteen vulnerabilities and two hardening measures, including five fixes in bundled Gutenberg JavaScript packages. Backports to eligible branches through 4.7 are in progress.

Why it matters

This is WordPress Core and bundled-editor exposure, not an optional plugin flaw. Both unauthenticated privilege escalation and a broken multisite administrator boundary are significant for operators. The issues have differing access prerequisites and should not be treated as one universally exploitable RCE. Patchstack notes that the published PHP file summary omits some Gutenberg package changes; patch audits must account for those. Neither WordPress nor Patchstack establishes active exploitation in the cited material.

The most consequential privilege-escalation paths

WordPress says unauthenticated manipulation of Template Part block attributes could escalate privileges and lead to remote code execution. Separately, a multisite site Administrator could take over a Super Admin account through Customizer menu previews. The exact exploit conditions for each path are not completely specified by the release announcement.

SQL injection, XSS and disclosure

Other fixes include SQL injection in WP_Meta_Query nested relation values and Customizer front-page previews; unauthenticated stored XSS through comment shortcode attributes; editor XSS through Openverse image metadata, media filenames and date formats; REST and XML-RPC information disclosure; and XML-RPC pingback denial of service. Required roles and conditions vary.

Gutenberg packages are part of the security patch

Patchstack reports five fixes from the bundled Gutenberg package update, including the Template Part issue. A partial diff based only on the documented PHP file list can miss these JavaScript changes. Custom deployment and integrity-check workflows should include the shipped assets.

Patching old branches

WordPress 7.1.5 is the current short-cycle security release. The project says backports for eligible historical branches through 4.7 are being shipped as ready. Operators on old branches must verify the actual patched version exists and is installed; the WordPress 7.2 release candidate is not a production substitute.

What to watch next

  • Confirmed exploitation and assigned CVEs.
  • Backport completion across historical branches.
  • Technical details about exploit prerequisites and remediation regressions.

Still unclear

  • No confirmed active exploitation was found in checked sources.
  • Exploit preconditions and affected-installation counts are not fully established.
  • Backport availability may change as releases ship.

Sources

Direct reading behind this dossier.

3 sources
WordPress 7.1.5 Release
WordPress.org primary/vendor

Official security fixes, update guidance and backports.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment