Threat reportVulnerabilityTL-2026-3259
WordPress 7.1.3 Security Release: Seven Fixes Including Stored XSS, Second-Order SQL Injection and Unauthenticated Comment Disclosure
WordPress 7.1.3 (released 2026-10-06) fixes seven security issues: stored XSS on the Comments admin page, XSS in Imgur embeds, second-order SQL injection in WXR export, unauthenticated disclosure of comments on private/unpublished posts, an Author-role sticky-post authorization weakness, forgeable {status}_{type} hook parameters, and a DoS in WP_Http::make_absolute_url().
Key facts
| Identifiers | TL-2026-3259 |
|---|---|
| Also known as | WordPress 7.1.3 Security Release |
| Severity | MEDIUM |
| Affected products | WordPress WordPress Core |
| Malware | PHP |
| MITRE ATT&CK techniques | T1059.007 JavaScript, T1078 Valid Accounts, T1190 Exploit Public-Facing Application, T1204.001 Malicious Link, T1213 Data from Information Repositories, T1499.004 Application or System Exploitation |
| Motivation | UNKNOWN |
| Target sectors | technology, news - media, ecommerce, government administration, education |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 7 cited sources |
Detection coverage
As of 2026-10-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-3259 across Splunk SPL, Microsoft KQL and Sigma, covering 8 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: WordPress WXR Single-Content-Type Export (Second-Order SQLi Trigger Path) — Exploitation
Detects an administrator-level download of /wp-admin/export.php for a single content type (content=<type>, not the default content=all). Per Patchstack, the second-order SQL injection via unsanitized _thumbnail_id post meta (present since 6.5.0, fixed in 7.1.3) is only reachable through this export path. On unpatched sites this request is the trigger for a previously planted payload; on any site it is a rare, high-value event worth reviewing.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1190, T1078
- Data sources: splunk:index=web sourcetype=access_combined, sentinel:W3CIISLog, sigma:webserver
- Severity: medium
- Confidence: medium
Splunk SPL
```WXR export trigger path: export.php?download=true&content=<single type> (not content=all)```
index=web sourcetype IN ("access_combined","apache:access","nginx:plus:kv") earliest=-24h
| eval q=lower(coalesce(uri_query,"")), p=lower(coalesce(uri_path,""))
| where match(p,"/wp-admin/export\.php$") AND match(q,"(^|&)download=true") AND match(q,"(^|&)content=[a-z0-9_-]+") AND NOT match(q,"(^|&)content=all(&|$)")
| stats count AS requests, min(_time) AS first_seen, max(_time) AS last_seen, values(status) AS statuses, values(q) AS query_strings BY src, user, host
| convert ctime(first_seen) ctime(last_seen)
| table first_seen last_seen host src user requests statuses query_stringsMicrosoft KQL
W3CIISLog
| where TimeGenerated > ago(24h)
| where csUriStem endswith "/wp-admin/export.php"
| where csUriQuery has "download=true" and csUriQuery has "content="
| where csUriQuery !has "content=all"
| summarize Requests = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Statuses = make_set(scStatus), Queries = make_set(csUriQuery, 10) by sSiteName, cIP, csUserName
| project FirstSeen, LastSeen, sSiteName, cIP, csUserName, Requests, Statuses, QueriesSigma
title: WordPress WXR Export of a Single Content Type (Second-Order SQLi Path)
id: 7c1e5a42-3b0d-4f6e-9a18-5d2f0b7e3c11
status: experimental
description: Detects requests to /wp-admin/export.php that download a single content type instead of the default "all content" export. The second-order SQL injection via unsanitized _thumbnail_id post meta (WordPress 6.5.0 - 7.1.2, fixed in 7.1.3) is reachable only through this export mode.
references:
- https://wordpress.org/news/?p=21753
- https://wordpress.org/documentation/wordpress-version/version-7-1-3/
- https://patchstack.com/articles/wordpress-7-1-3-security-release/
author: Threadlinqs Team
date: 2026-10-10
tags:
- attack.initial-access
- attack.t1190
- attack.t1078
logsource:
category: webserver
detection:
selection:
c-uri|contains: '/wp-admin/export.php'
cs-uri-query|contains|all:
- 'download=true'
- 'content='
filter_all_content:
cs-uri-query|contains: 'content=all'
condition: selection and not filter_all_content
fields:
- c-ip
- c-uri
- cs-uri-query
- sc-status
falsepositives:
- Administrators legitimately exporting a single post type (posts, pages, media) for migration or backup
level: mediumKnown false positives:
- Administrators exporting a single post type for site migration or backup
- Scheduled content-migration tooling using export.php
Tuning notes: Allow-list known admin source IPs/accounts and migration windows. Pair with DB-side detection TL-2026-3259-SIG-002 (non-numeric _thumbnail_id) to raise confidence. Version-gate to hosts still on WordPress 6.5.0-7.1.2 via CMDB/asset inventory.
- Pending Comment with HTML-Injecting Link href (Comments Admin Stored XSS) — Exploitation · unlock with TL Creds
- REST API Sticky-Post Change via /wp/v2/posts (Author-Role Capability Bypass) · unlock with TL Creds
- Privileged Admin Action Forged from Comments Page (Post-Click Stored-XSS Session Abuse) · unlock with TL Creds
- Imgur oEmbed Proxy Request (Incorrectly Whitelisted oEmbed Provider XSS) — Exposure Hunting · unlock with TL Creds
- Non-Numeric _thumbnail_id Post Meta Written to Database (Second-Order SQLi Payload Staging) · unlock with TL Creds
- Forged post_status/post_type Parameters Colliding with Core Action Names ({status}_{type} Hook) · unlock with TL Creds
- Unauthenticated Single-Post Feed Enumeration — Private/Unpublished Comment Disclosure · unlock with TL Creds
- WP_Http::make_absolute_url() Infinite-Loop DoS — PHP Execution Timeout in class-wp-http.php · unlock with TL Creds
Indicators of compromise
As of 2026-10-10, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-3259.
Technical analysis
No CVE IDs, CVSS scores, exploitation reports or public PoCs are stated in the sources.
WordPress 7.1.3 is a maintenance and security release published on 2026-10-06 (release leader Jake Spurlock) containing seven security fixes and four bug fixes. The vendor recommends updating immediately. The release is the third WordPress security update in 19 days, following 7.1.1 (2026-09-17) and 7.1.2 (2026-09-22). Fixes are backported to branches eligible for security fixes (currently through 4.7), although Patchstack noted that at publication time backports were available through 6.6 with 4.7-6.5 pending. Only the most recent WordPress version is actively supported.
Stored XSS on the Comments administration page (reported by Trail of Bits in collaboration with OpenAI; Cyber Security News credits Thomas Chauchefoin): per Patchstack the attack vector is a malicious link in a pending comment, requiring a moderator to click it, and affects 7.1.0-7.1.2. The root cause is jQuery's $() function processing link href attributes from pending comments as HTML, tied to class attributes added in 7.1.0. Imgur embeds were vulnerable to XSS (reported by Zhengyu Liu, Jingcheng Yang and Gavin Zhong): Patchstack states Imgur was incorrectly whitelisted as a trusted oEmbed provider, bypassing sandbox filtering of user-supplied content; cached oEmbed content persists after the update and may need to be cleared manually.
Second-order SQL injection in WXR export (reported by Anthropic): per Patchstack, unsanitized _thumbnail_id post metadata is used when an administrator exports a single content type (not the default 'All content' export); present since 6.5.0. Unauthenticated disclosure of comments on private and unpublished posts (reported by Ananda Dhakal, Patchstack): per Patchstack, comment visibility checks occurred after query execution, allowing unauthenticated access via a single-post feed. A weakness allowing Author-role users to make posts sticky (reported by Anthropic) is a REST API capability bypass. Forgeable parameters passed to the {status}_{type} hook can lead to action name collision (reported by Alex Concha of the WordPress security team); Patchstack says exploitation requires a dependent plugin plus post data manipulation. A DoS in WP_Http::make_absolute_url() (reported by Anthropic) is an infinite loop triggered via a regex pattern and requires Contributor+ access per Patchstack.
Revised files: /wp-admin/js/common.js, /wp-admin/includes/export.php, class-wp-rest-posts-controller.php, class-wp-customize-manager.php, class-wp-customize-setting.php, class-wp-http.php, class-wp-oembed.php, class-wp-query.php and post.php. No packages were revised. No CVE identifiers, CVSS scores, exploitation in the wild, public PoCs or CISA KEV listing are stated in any source; the Cyber Security News headline calling these 'critical' is not an official severity classification. Severity is set to MEDIUM by analyst judgment. No network IOCs were published, so no BeaconBeagle correlation applies.
MITRE ATT&CK techniques by tactic:
Execution
T1059.007 JavaScript; T1204.001 Malicious Link
Initial Access
T1078 Valid Accounts; T1190 Exploit Public-Facing Application
Collection
T1213 Data from Information Repositories
Impact
Remediation
Patches
- WordPress 7.1.3
- Backports to older branches eligible for security fixes (through 4.7 per the announcement; Patchstack reported availability through 6.6 at publication)
Immediate actions
- Update to WordPress 7.1.3 via Dashboard > Updates or wordpress.org/download/releases
- Clear cached oEmbed content after updating so pre-existing malicious Imgur embeds are not rendered
- Review pending comments before moderating and avoid clicking links inside them until patched
Workarounds
- Until patched, avoid single-content-type WXR exports
- Restrict Contributor+ accounts and review feed exposure for private/unpublished posts
Longer-term hardening
- Enable automatic background security updates for WordPress core
- Audit Contributor and Author role assignments and apply least privilege
- Move off unsupported WordPress branches; only the latest version is actively supported
Affected and fixed versions
- WordPress — WordPress Core
Vulnerable versions: 7.1.0-7.1.2 (Comments admin stored XSS); 6.5.0 and later (WXR export SQL injection); older branches eligible for security fixes, through 4.7
Fixed in: 7.1.3
Timeline
- WordPress 7.1.1 released, the first of three security updates in 19 days (per drweb.de)
- WordPress 7.1.2 released as an emergency patch (per drweb.de)
- Anthropic AI-driven security research had disclosed 6,157 flaws across 591 projects as of this date (per drweb.de)
- Patchstack published technical analysis; backports available through 6.6, with 4.7-6.5 pending at publication
- WordPress 7.1.3 released with seven security fixes and four bug fixes; immediate update recommended
- Cyber Security News published coverage of the seven fixes
- Official 7.1.3 release notes page last modified
Sources cited
- WordPress Version 7.1.3 release notes wordpress.org · Advisory · 2026-10-06
- WordPress HackerOne responsible disclosure program hackerone.com · Advisory · 2026-10-06
- WordPress 7.1.3 Maintenance and Security Release wordpress.org · Vendor report · 2026-10-06
- Patchstack: WordPress 7.1.3 Security Release patchstack.com · Research · 2026-10-06
- Pantheon release notes: WordPress 7.1.3 docs.pantheon.io · Vendor report · 2026-10-06
- Critical WordPress Vulnerabilities Enable XSS, SQL Injection and Data Disclosure Attacks cybersecuritynews.com · News · 2026-10-07
- drweb.de: WordPress 7.1.3 - das dritte Sicherheitsupdate in 19 Tagen drweb.de · News · 2026-10-06
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.