# WordPress 7.1.5 Security Release: 20 Core Fixes Including Template Part Block Permission Flaw (Potential RCE) and SQL Injection in WP_Meta_Query / Customizer Previews

> WordPress 7.1.5 (released 2026-11-18) patches 20 security items in WordPress Core, including an unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, two SQL injections (WP_Meta_Query, Customizer changeset front-page previews), unauthenticated stored XSS in comments, and a multisite Administrator-to-Super Admin takeover. No in-the-wild exploitation, PoC, CVE IDs or CVSS scores have been published.

- **Published:** 2026-11-19T02:35:10Z
- **Last reviewed:** 2026-11-19T02:35:10Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6401
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6401.png
- **ID:** TL-2026-6401
- **Severity:** HIGH
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 12

## Description

On 2026-11-18 the WordPress project shipped 7.1.5, a security release recommended for immediate update. The official announcement lists 20 items: 19 vulnerability fixes plus one hardening change (removal of the block editor's Imgur embed variation, whose server-side provider no longer exists). A second hardening fix corrects a malformed regular expression that broadened JSON media type matching, reported by the WordPress Security Team.

The highest-impact items are: (1) an unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution (reported by Logan Homolka); the source does not identify which configurations are exploitable and no attacks are reported; (2) SQL injection in WP_Meta_Query via nested relation values (Christiaan Swiers); (3) SQL injection via the front page setting in Customizer changeset previews (Rudy Faile, WordPress Security Team); (4) unauthenticated stored XSS via shortcode attributes in comments (Rafie Muhammad, Awesome Motive); and (5) a multisite privilege escalation allowing a site Administrator to take over a Super Admin account through Customizer menu previews (Yuval Miller).

Other fixes cover: unauthenticated denial of service via batched XML-RPC pingbacks (Giovanni Cintolo); unauthenticated disclosure of private taxonomy terms via the REST API search endpoint (Anthropic); Author+ disclosure of user email addresses via the REST API comments endpoint; Editor+ disclosure via post and template author assignment in the REST API; Subscriber+ disclosure via XML-RPC wp.getComments; an Author+ authorization bypass via comment editing in the admin; and several XSS issues (legacy media library popup reflected XSS, wp_interactivity_data_wp_context() store namespace, oEmbed provider responses, Administrator stored XSS in Customizer previews, Comment Date block date format, Openverse image metadata in the block editor, and media filenames when converting a media block to a File block).

The HelpHub 7.1.5 page states that WordPress 7.0 and every branch through 6.5 are affected by all 20 issues, with fewer affected in older branches (e.g. 4.7 is affected by 11 of 20). Courtesy backports were released for every branch back to 4.7 (e.g. 7.0.9, 6.9.12, 6.8.13, 4.7.40); 4.6 and earlier receive no security updates. Files revised include class-wp-meta-query.php, class-wp-query.php, class-wp-customize-manager.php, class-wp-customize-nav-menus.php, class-wp-customize-setting.php, class-wp-xmlrpc-server.php, class-wp-oembed-controller.php, shortcodes.php, formatting.php, load.php, rest-api.php, several REST controllers, comment-date.php and wp-admin/includes/comment.php. WordPress 7.2 RC2 contains the fixes; 7.2 is planned for 2026-12-08.

Defender note: no exploitation is reported and no technical detail beyond one-line descriptions is public. Severity HIGH is an analyst assessment based on the network-reachable unauthenticated vulnerability classes and the large WordPress install base, not a vendor-stated rating. The prior 7.1.2-7.1.4 releases are reported as separate issues.

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1059.007 Command and Scripting Interpreter: JavaScript
- T1499.004 Endpoint Denial of Service: Application or System Exploitation
- T1589.002 Gather Victim Identity Information: Email Addresses

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Web Server / PHP-FPM Spawning Shell After WordPress Exploitation - Post-Exploitation** (`TL-2026-6401-SPL-002`)

TL-2026-6401: Detects php-fpm, apache2, httpd or nginx parent processes spawning sh, bash, curl, wget, nc, python or perl. The Template Part block privilege escalation is described as potentially leading to RCE; a shell child of the web tier is the highest-fidelity post-exploitation signal even without exploit specifics.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1505.003, T1059.004, T1190
- **Data sources:** endpoint_datamodel, mde_deviceprocessevents, sysmon_linux_or_auditd
- **Severity:** high
- **Confidence:** high

### Splunk SPL

````spl
| tstats summariesonly=false count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.parent_process_name IN ("php-fpm","php-fpm7.4","php-fpm8.0","php-fpm8.1","php-fpm8.2","php-fpm8.3","php-cgi","apache2","httpd","nginx") AND Processes.process_name IN ("sh","bash","dash","busybox","nc","ncat","curl","wget","python","python3","perl") by Processes.dest Processes.user Processes.parent_process_name Processes.process_name Processes.process
```TL-2026-6401 web server or PHP-FPM spawning a shell or download tool after WordPress exploitation (potential RCE via Template Part block)```
| rename Processes.* as *
| convert ctime(firstTime) ctime(lastTime)
| sort - count
````

### Microsoft KQL

```kql
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ ("php-fpm","php-fpm7.4","php-fpm8.0","php-fpm8.1","php-fpm8.2","php-fpm8.3","php-cgi","apache2","httpd","nginx")
| where FileName in~ ("sh","bash","dash","busybox","nc","ncat","curl","wget","python","python3","perl")
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine
| order by Timestamp desc
```

### Sigma

```yaml
title: WordPress Web Server Process Spawning Shell or Download Utility
id: c5f7d9e3-2b4a-4c86-9d0f-3a1b2e4c5d04
status: experimental
description: Detects a web server or PHP handler spawning a shell, scripting interpreter or download utility, the expected post-exploitation behaviour if the WordPress 7.1.5 Template Part block flaw (potential RCE) is abused (TL-2026-6401).
references:
    - https://wordpress.org/news/2026/11/wordpress-7-1-5-release/
    - https://wordpress.org/documentation/wordpress-version/version-7-1-5/
author: Threadlinqs Team
date: 2026/11/19
tags:
    - attack.persistence
    - attack.t1505.003
    - attack.execution
    - attack.t1059.004
logsource:
    category: process_creation
    product: linux
detection:
    selection_parent:
        ParentImage|contains:
            - '/php-fpm'
            - '/php-cgi'
            - '/apache2'
            - '/httpd'
            - '/nginx'
    selection_child:
        Image|endswith:
            - '/sh'
            - '/bash'
            - '/dash'
            - '/busybox'
            - '/nc'
            - '/ncat'
            - '/curl'
            - '/wget'
            - '/python'
            - '/python3'
            - '/perl'
    condition: selection_parent and selection_child
falsepositives:
    - Plugins that shell out to curl, wget or python for image or backup handling
    - Administrative cron wrappers launched from PHP
level: high

```

**Known false positives:**

- WordPress plugins invoking curl or wget through exec()
- Backup or image-optimisation plugins calling shell tools

**Tuning notes:** Baseline legitimate command lines per host for 14 days and exclude exact matches. Restrict to hosts tagged as WordPress servers. Escalate on base64, /dev/tcp, chmod +x or writes to /tmp.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- WordPress 7.1.5 Unauthenticated Template Part Block Write (Privilege Escalation) - Exploitation (locked: unlock with TL Creds)
- PHP Web Shell in WordPress Uploads or Core File Tampering - Post-Exploitation (locked: unlock with TL Creds)
- WordPress REST / XML-RPC Enumeration of Emails, Comments and Private Terms - Reconnaissance (locked: unlock with TL Creds)
- WordPress 7.1.5 XSS Payload Against Media Popup / oEmbed / Comments - Exploitation (locked: unlock with TL Creds)
- WordPress Multisite Super Admin Takeover via Customizer Menu Preview - Post-Exploitation (locked: unlock with TL Creds)
- Web Server Outbound Connection on Non-Standard Port (Reverse Shell / C2) - C2 (locked: unlock with TL Creds)
- WordPress 7.1.5 SQL Injection Probing (WP_Meta_Query / Customizer Changeset) - Exploitation (locked: unlock with TL Creds)
- WordPress XML-RPC Batched Pingback Denial of Service - Impact (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [WordPress 7.1.5 Security Release (official announcement)](https://wordpress.org/news/2026/11/wordpress-7-1-5-release/)
- [WordPress Version 7.1.5 (HelpHub release notes, affected branches and revised files)](https://wordpress.org/documentation/wordpress-version/version-7-1-5/)
- [WordPress 7.1.5 Patches 20 Security Issues, Including Potential RCE and SQL Injection Flaws](https://cybersecuritynews.com/wordpress-7-1-5-patches-20-security-issues/)
- [WordPress Version 7.0.9](https://wordpress.org/documentation/wordpress-version/version-7-0-9/)
- [WordPress Version 6.9.12](https://wordpress.org/documentation/wordpress-version/version-6-9-12/)
- [WordPress Version 4.7.40](https://wordpress.org/documentation/wordpress-version/version-4-7-40/)
- [Cyber Security News: WordPress 7.1.4 fixes security flaws (prior related release)](https://cybersecuritynews.com/wordpress-7-1-4-fixes-security-flaws/)
- [WordPress HackerOne program (responsible disclosure channel cited by the release)](https://hackerone.com/wordpress?type=team)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6401
