WordPress 7.1.5: Template Part Link Turns Admin Into Code - Floor 7.1.5

WordPress shipped 7.1.5 on 18 November 2026 as a security release. HelpHub and the news post list 20 items. GitHub has 19 advisories dated that day on WordPress/wordpress-develop - five High, five Medium, nine Low - plus a hardening that removes the dead Imgur embed variation. No CVE IDs on those GHSA objects. No CVSS vector on them either. GitHub's own severity field is what we use below.[1][2][3]
The one that matters on a shared box first is GHSA-pmp8-6cv8-q323 (High): Template Part theme / slug attributes can make an Administrator's editor hit another URL on the same site. An Author or above can plant them in a post. An unauthenticated attacker can send the Administrator a crafted editor link. When that admin opens it, GitHub says this can create an Administrator account for the attacker, and that account can run code through plugin upload.[3]
This is not the 7.1.4 upgrade-window race (CVE-2026-119977, KEV 3 Nov). Core 7.1.4 does not make 7.1.5. PHP 8.5.13 does not either.[4][10]
Not on CISA KEV. Catalog 2026.11.20, 1,790 entries, dateReleased 2026-11-20T17:48:39.1516Z. Newest rows are Apache Roller, VMware vCenter, SAP NetWeaver, Cisco Expressway. The WordPress KEV still on the list is CVE-2026-119977 (7.1.4), not these GHSAs.[10]
If you host WordPress on cPanel, Plesk, LiteSpeed, or a VPS, this is today's Core floor.
What it is
Vendor-published facts:
- GHSA-pmp8-6cv8-q323 (High): Template Part
themeandslugattributes. Author+ can set them. Unauthenticated attacker can send an Administrator a crafted editor link or redirect them to one. Opening it can create an Administrator. GitHub: that allows code execution through plugin upload. Backported to 5.9. Reporter: logansec (Logan Homolka on the news post).[1][3] - GHSA-cr2m-2j4r-3v3x (High): Unauthenticated stored XSS via a comment shortcode whose escaped attribute decoded into HTML after sanitization, then rendered by a Comments / Latest Comments block. Backported to 4.7. Reporter: rafiem.[5]
- GHSA-gm52-6h3w-97v4 (High): Reflected XSS in the legacy media library popup. Crafted link; a logged-in user who can upload files opens it; script runs in wp-admin. Anthropic. To 4.7.[6]
- GHSA-jmhp-hg7w-w9c5 (High): Openverse creator metadata pasted into an image caption without escaping. No account required to poison the metadata; script runs when an editor inserts that image from Openverse search. To 6.2. Reporter: kq5y.[7]
- GHSA-mwj7-xhp9-7773 (High): Multisite. Site Administrator replays a Customizer widget hash as the signature for nav menu selective refresh, runs a callback, takes over Super Admin. Needs a classic theme with widgets enabled. To 4.7. Reporter: yuvalmiller.[8]
- Medium, still operator-relevant: GHSA-xc9c-4hg4-h4jg -
WP_Meta_Querynestedrelationinto SQL when a plugin/theme passes untrusted nestedmeta_query(to 4.7); GHSA-rcr3-43fx-wqfv - unauthenticated REST search leaking private taxonomy terms including nav menus (to 5.6); GHSA-56j2-5mp6-wr3x - unauthenticated XML-RPCsystem.multicallpingback DoS (one second + outbound HTTP per pingback, to 4.7); GHSA-mcv9-c2pg-6m4v - SQLi via Customizer front-page setting in changeset previews.[2][9]
We did not open a crafted editor URL or plant Template Part attributes. Do not paste a "how to reproduce" into a ticket.
This is not:
- CVE-2026-119977 / 7.1.4 upgrade-window RCE (KEV 3 Nov). Different files (
class-wp-upgrader.phpthen; templates REST / block attributes now).[4][10] - PHP 8.5.13 / 8.4.28 (19 Nov). Core updates do not replace
php-fpm/lsphp. - cPanel 138.0.25 WP Toolkit proxy or 138.0.28 reseller-SSL. Those are panel floors.
How serious is it?
GitHub High on five issues. WordPress.org did not publish CVSS. Do not invent a 9.8.
pmp8 is not unauthenticated RCE with zero interaction. The GHSA is explicit: someone with Administrator in the browser has to open the editor link (or an Author+ post already carries the attributes and an admin opens the editor). After that, GitHub's impact is new Administrator → plugin upload → code. Treat that as stored/CSRF-shaped privilege escalation to RCE, not as an unauth internet 9.8.[3]
cr2m is unauthenticated stored XSS in comments. That is a different, lower-friction High if comments are open.[5]
No in-the-wild statement on the 19 GHSAs or the 7.1.5 news post. Not KEV. Absence from KEV is not "scanners will wait." Two of the last three Core security releases (7.1.2, 7.1.4) were probed or KEV'd on a short clock; that history is not proof these 19 are being exploited today.[1][10]
Who is affected
HelpHub branch floors (18 Nov). 7.0 through 6.5 get all 20. Older branches get fewer because the code is not there:[2]
- 7.1 → 7.1.5 (all 20)
- 7.0 → 7.0.9
- 6.9 → 6.9.12
- 6.8 → 6.8.13
- 6.7 → 6.7.12
- 6.6 → 6.6.12
- 6.5 → 6.5.15
- 6.4 → 6.4.15 (19 of 20)
- 6.3 → 6.3.15 (19)
- 6.2 → 6.2.16 (19)
- 6.1 → 6.1.17 (18)
- 6.0 → 6.0.19 (18)
- 5.9 → 5.9.21 (17) - Template Part (pmp8) starts here
- 5.8 → 5.8.20 through 5.6 → 5.6.24 (15)
- 5.5 → 5.5.25 through 5.1 → 5.1.29 (13)
- 5.0 → 5.0.32, 4.9 → 4.9.36, 4.8 → 4.8.35 (12)
- 4.7 → 4.7.40 (11)
Out of scope unless you still run it:
- 4.6 and earlier - WordPress will not ship these fixes. Move the site or take it off the internet.[2]
- A box on 7.1.5 Core with an old PHP binary. Wrong column; yesterday's floor still applies.
What to do now
- Read the Core version the site actually runs, not the panel "WordPress" badge.
wp core version --allow-root
# or:
grep wp_version wp-includes/version.php
Want 7.1.5 on current, or the HelpHub row for that branch (7.0.9 / 6.9.12 / 6.8.13 / … / 4.7.40). 7.1.4 is last month.
- Update Core, then confirm the file on disk. Auto background updates can be off (host, plugin,
DISALLOW_FILE_MODS, Composer/Git).
wp core update --allow-root
wp core version --allow-root
# pin an older branch, example:
# wp core update --version=6.8.13 --allow-root
cPanel WP Toolkit / Plesk WP Toolkit: mass-update from the panel, then spot-check version.php on a sample of accounts. Toolkit ≠ Core.
-
Until Core is new: tell Administrators not to open unexpected
wp-admineditor / site-editor / Customizer links. That is the pmp8 click. It is a stopgap, not a patch.[3] -
Comments: if you cannot update today, hold comments for moderation (
Settings → Discussion). That shrinks cr2m. It does not cover Template Part or Super Admin takeover.[5] -
After the update: list Administrator (and Super Admin on multisite) users you did not add. Look at
wp-content/plugins/mtime after 18 Nov. Plugin upload is the RCE GitHub named, not a magic webshell string.[3] -
XML-RPC: if nothing uses pingbacks, deny
xmlrpc.phpat the vhost. That is the 56j2 DoS path. It is not the Template Part fix.[9]
Versions with no WordPress.org floor
4.6 and earlier get nothing. Isolate, then migrate to a maintained branch. A WAF is not Core.[2]
Composer / Bedrock / git-deployed trees update only when your pipeline ships wordpress/wordpress (or the distro package). Dashboard "Update Now" will not save you if DISALLOW_FILE_MODS is on.
Compromise signs
None of these prove pmp8 by themselves.
- New
Administrator/ Super Admin users dated after 18 Nov that nobody on the ticket created. - Plugin zips or MU-plugins under
wp-contentyou did not deploy, same window. - Administrators reporting they opened a "fix the template" / site-editor link they did not expect.
wp core versionstill on 7.1.4 / 7.0.8 / 6.9.11 (or the 7.1.4 HelpHub row) after you thought 7.1.5 landed.
The GHSAs publish no log signature. Do not grep for a path we invented.
FAQ
Is this the 7.1.4 upgrade-window RCE? No. That was CVE-2026-119977 (KEV 3 Nov). 7.1.4 randomizes the staging dir. 7.1.5 is Template Part / comments / REST / Customizer. Install 7.1.5 anyway.[1][4][10]
Is it unauthenticated RCE if nobody clicks? Not as GitHub wrote pmp8. Unauthenticated attacker sends the link; Administrator opens the editor. Author+ can pre-plant attributes. cr2m (comment XSS) does not need an admin click if comments render.[3][5]
Did WordPress assign CVEs? Not on the 19 GHSA JSON objects we pulled. Do not mint IDs.
Does PHP 8.5.13 cover this? No. Different binary. Patch both.
Does upcp / Plesk MU cover this? Only if Toolkit actually moved Core. Check version.php.
Is it on KEV? No. Catalog 2026.11.20 / 1,790. WordPress on that catalog is still 119977.[10]
Gutenberg as a plugin? Core ships the block editor. We did not verify a separate wordpress.org plugin release in this run. If gutenberg is an active plugin, update it from the dashboard after Core; do not skip Core because of it.
What we are not claiming
- We did not exploit Template Part attributes, comment shortcodes, or Customizer hashes.
- No in-the-wild / ransomware statement from WordPress.org or these GHSAs.
- No CVSS on the GitHub objects - do not quote a third-party 8.1/9.8 as WordPress.org's.
- We did not inventory every host's WP Toolkit auto-update policy.
- LiteSpeed 6.3.7 Build 10 (20 Nov: HTTP/3 / LSAPI / suEXEC-timing) and Plesk NGINX 1.30.7 / CVE-2026-123007 are different floors. Same week, not this bug.
Sources
[1] https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ [2] https://wordpress.org/documentation/wordpress-version/version-7-1-5/ [3] https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-pmp8-6cv8-q323 [4] https://wordpress.org/news/2026/10/wordpress-7-1-4/ [5] https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-cr2m-2j4r-3v3x [6] https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-gm52-6h3w-97v4 [7] https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jmhp-hg7w-w9c5 [8] https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-mwj7-xhp9-7773 [9] https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-56j2-5mp6-wr3x [10] https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json