Skip to navigation

Threat reportVulnerabilityTL-2026-6401

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

highPATCHED

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.

Key facts

IdentifiersTL-2026-6401
Also known asWordPress 7.1.5 Security Release
SeverityHIGH
First disclosed
Affected productsWordPress WordPress Core
Weaknesses (CWE)CWE-89, CWE-79, CWE-269, CWE-200, CWE-400, CWE-285
MalwarePHP, PingBack
MITRE ATT&CK techniquesT1059.007 Command and Scripting Interpreter: JavaScript, T1190 Exploit Public-Facing Application, T1499.004 Endpoint Denial of Service: Application or System Exploitation, T1589.002 Gather Victim Identity Information: Email Addresses
MotivationUNKNOWN
Target sectorstechnology, news - media, ecommerce, government administration, education
Target regionsGlobal
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-11-19, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6401 across Splunk SPL, Microsoft KQL and Sigma, covering 12 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Web Server / PHP-FPM Spawning Shell After WordPress Exploitation - Post-Exploitation

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

| 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

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

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. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • WordPress 7.1.5 Unauthenticated Template Part Block Write (Privilege Escalation) - Exploitation · unlock with TL Creds
  • PHP Web Shell in WordPress Uploads or Core File Tampering - Post-Exploitation · unlock with TL Creds
  • WordPress REST / XML-RPC Enumeration of Emails, Comments and Private Terms - Reconnaissance · unlock with TL Creds
  • WordPress 7.1.5 XSS Payload Against Media Popup / oEmbed / Comments - Exploitation · unlock with TL Creds
  • WordPress Multisite Super Admin Takeover via Customizer Menu Preview - Post-Exploitation · unlock with TL Creds
  • Web Server Outbound Connection on Non-Standard Port (Reverse Shell / C2) - C2 · unlock with TL Creds
  • WordPress 7.1.5 SQL Injection Probing (WP_Meta_Query / Customizer Changeset) - Exploitation · unlock with TL Creds
  • WordPress XML-RPC Batched Pingback Denial of Service - Impact · unlock with TL Creds

Indicators of compromise

As of 2026-11-19, Threadlinqs Intelligence tracks 12 indicators of compromise for TL-2026-6401.

12 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

No in-the-wild exploitation, PoC, CVE IDs or CVSS scores have been published.

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 techniques by tactic:

Execution

T1059.007 Command and Scripting Interpreter: JavaScript

Initial Access

T1190 Exploit Public-Facing Application

Impact

T1499.004 Endpoint Denial of Service: Application or System Exploitation

Reconnaissance

T1589.002 Gather Victim Identity Information: Email Addresses

Remediation

Patches

  • WordPress 7.1.5
  • Backports: 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, 5.8.20, 5.7.22, 5.6.24, 5.5.25, 5.4.26, 5.3.28, 5.2.31, 5.1.29, 5.0.32, 4.9.36, 4.8.35, 4.7.40
  • WordPress 7.2 RC2 contains the fixes; 7.2 planned for 2026-12-08

Immediate actions

  • Update WordPress Core to 7.1.5 (Dashboard > Updates > Update Now) and confirm the installed version
  • Verify that automatic background updates actually applied on managed and multisite installs
  • If on an older branch, move to the patched backport for that branch (e.g. 7.0.9, 6.9.12, 6.8.13, 4.7.40)

Workarounds

  • None published by the vendor; if XML-RPC is not needed, consider disabling it to reduce exposure to the pingback DoS and wp.getComments disclosure items (analyst suggestion, not vendor guidance)

Longer-term hardening

  • Move off unsupported branches: WordPress 4.6 and earlier receive no security updates and only the latest version is actively supported
  • Restrict Contributor/Author/Editor roles and review multisite Administrator assignments
  • Monitor REST API, XML-RPC and Customizer changeset requests for anomalous use

Affected and fixed versions

  • WordPress — WordPress Core
    Vulnerable versions: 7.1.0-7.1.4; 7.0.x before 7.0.9; 6.9.x before 6.9.12; 6.8.x before 6.8.13; 6.5-6.7 (all 20 issues); 4.7 through 6.4 (11-19 of 20 issues depending on branch)
    Fixed in: 7.1.5; 7.0.9; 6.9.12; 6.8.13; 6.7.12; 6.6.12; 6.5.15; 6.4.15; 4.7.40

Timeline

  • WordPress 7.1.2 released with a separate critical fix (reported by third-party coverage as an unauthenticated file inclusion, CVE-2026-87902); unrelated to the 7.1.5 items
  • WordPress 7.1.4 released, fixing a separate update-process weakness per Cyber Security News
  • WordPress 7.2 RC2 released containing the applicable security fixes
  • Courtesy backports released for all branches back to 4.7 (e.g. 7.0.9, 6.9.12, 6.8.13, 4.7.40); 4.6 and earlier unsupported
  • WordPress 7.1.5 security release published fixing 20 Core items (19 vulnerabilities plus one hardening change); updating immediately recommended
  • Cyber Security News reports the release, highlighting the Template Part block potential RCE and SQL injection flaws; no exploitation, CVEs or CVSS scores reported
  • WordPress 7.2 major release planned (upcoming)

Sources cited

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats