WordPress 7.1.5 Security Release Fixes High-Severity Privilege Escalation

WordPress 7.1.5 fixes 20 listed security items, including a high-severity unauthenticated privilege-escalation issue that requires an Administrator to open a crafted editor link. WordPress recommends updating immediately.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Original editorial illustration of a blue checkmark shield between server racks and abstract code panels.
Act now: WordPress says 7.1.5 is a security release with fixes for multiple issues and recommends updating sites immediately.[1]
Released
November 18, 2026[2]
Highlighted issue
Unauthenticated privilege escalation that could lead to remote code execution[1]
Advisory status
High severity; no known CVE[3]

What the high-severity advisory says

The GitHub advisory says an unauthenticated attacker could send an Administrator a crafted editor link or redirect the Administrator to one.[3]

The privilege-escalation chain requires the Administrator to open it; the advisory says that action could create an Administrator account for the attacker, enabling code execution through plugin upload.[3]

The official release and HelpHub each list 20 security items.[1][2]

That list is not 20 identical vulnerability classes: it explicitly includes a malformed-regular-expression hardening measure and a separate hardening change that removes an obsolete Imgur embed variation.[1]

Affected and patched versions for GHSA-pmp8-6cv8-q323

Affected range Patched version
7.1.0–7.1.4 7.1.5[3]
7.0.0–7.0.8 7.0.9[3]
6.9.0–6.9.11 6.9.12[3]
6.8.0–6.8.12 6.8.13[3]
6.7.0–6.7.11 6.7.12[3]
6.6.0–6.6.11 6.6.12[3]
6.5.0–6.5.14 6.5.15[3]
6.4.0–6.4.14 6.4.15[3]
6.3.0–6.3.14 6.3.15[3]
6.2.0–6.2.15 6.2.16[3]
6.1.0–6.1.16 6.1.17[3]
6.0.0–6.0.18 6.0.19[3]
5.9.0–5.9.20 5.9.21[3]

What site owners should do

Practical guidance: Update immediately.[1]

WordPress documents two official routes: Dashboard > Updates in the site admin area, or the WordPress release archive.[2][4]

For sites that support automatic background updates, WordPress says the update process begins automatically.[1]

Backport boundary

HelpHub lists courtesy fixes through WordPress 4.7 and says WordPress 4.6 and earlier no longer receive security updates; the GitHub advisory’s affected-and-patched table for this highlighted privilege-escalation issue runs from 7.1 through 5.9.[2][3]

Reporting cutoff: November 22, 2026 at 13:24:55 UTC.

Sources

  1. WordPress 7.1.5 Release — accessed 2026-11-22T13:24:55Z
  2. WordPress Version 7.1.5 HelpHub documentation — accessed 2026-11-22T13:24:55Z
  3. GitHub advisory GHSA-pmp8-6cv8-q323 — accessed 2026-11-22T13:24:55Z
  4. WordPress Release Archive — accessed 2026-11-22T13:24:55Z