Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-60137.
Upgrade to ProWordPress Core SQL Injection Exploitation (CVE-2026-60137)
Detects exploitation attempts and successful exploitation of CVE-2026-60137, a SQL injection vulnerability (CWE-89) in WordPress Core affecting unauthenticated or authenticated request handling. This vulnerability is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and is actively being exploited in the wild. Exploitation typically manifests as anomalous SQL syntax in HTTP request parameters targeting WordPress endpoints (wp-admin, wp-json REST API, xmlrpc.php, plugin/theme AJAX handlers), followed by unusual database error responses, data exfiltration patterns, or subsequent webshell/backdoor deployment. WordPress 7.0.2 remediates this issue; unpatched sites remain at critical risk per CISA BOD 26-04 prioritization guidance.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- WordPress
- Product
- Core
Weakness (CWE)
Timeline
- Disclosed
- July 21, 2026
References & Proof of Concept
- https://wordpress.org/news/2026/07/wordpress-7-0-2-release/
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-60137
What is CVE-2026-60137 WordPress Core SQL Injection Exploitation (CVE-2026-60137)?
WordPress Core SQL Injection Exploitation (CVE-2026-60137) (CVE-2026-60137) maps to the Initial Access and Execution and Credential Access tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for WordPress Core SQL Injection Exploitation (CVE-2026-60137), covering the data sources and telemetry it touches: IIS Logs, Web Application Firewall Logs, Azure Front Door Logs. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
let SuspiciousPatterns = dynamic(["UNION SELECT","UNION ALL SELECT","' OR '1'='1","information_schema","SLEEP(","benchmark(","0x2727","CONCAT(0x","--+-","xp_cmdshell"]);
W3CIISLog
| where csUriStem has_any ("/wp-admin", "/wp-json", "/xmlrpc.php", "/wp-content/plugins", "/wp-content/themes")
| where csUriQuery has_any (SuspiciousPatterns) or csUriStem has_any (SuspiciousPatterns)
| extend DecodedQuery = url_decode(csUriQuery)
| where DecodedQuery has_any (SuspiciousPatterns)
| summarize RequestCount = count(), Methods = make_set(csMethod), SampleURIs = make_set(csUriQuery, 5) by cIP, csUriStem, sSiteName, bin(TimeGenerated, 5m)
| where RequestCount >= 3
| order by RequestCount desc Detects SQL injection payload patterns in HTTP requests to WordPress core endpoints, consistent with CVE-2026-60137 exploitation attempts against unpatched sites (pre-7.0.2).
Data Sources
Required Tables
False Positives
- Security scanners and authorized penetration testing tools generating SQLi test payloads
- Legitimate content containing SQL-like keywords in blog posts or comments being URL-encoded
- Overly broad WAF logging capturing benign query strings with coincidental keyword matches
Sigma rule & cross-platform mapping
The detection logic for WordPress Core SQL Injection Exploitation (CVE-2026-60137) (CVE-2026-60137) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: network_connection
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-60137
References (4)
- https://wordpress.org/news/2026/07/wordpress-7-0-2-release/
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-60137
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulate SQLi Probe Against wp-json Endpoint
Expected signal: Web server access log entry with URI query containing 'UNION SELECT' and 'wp_users' targeting /wp-json/wp/v2/posts.
- Test 2Simulate SQLi Probe Against xmlrpc.php
Expected signal: Web access log entry showing xmlrpc.php request with "' OR '1'='1" in the query string.
- Test 3Simulate Time-Based Blind SQLi Probe
Expected signal: Web access log entry for admin-ajax.php containing 'SLEEP(5)' with an observable elevated response time in the log or APM data.
- Test 4Simulate Successful SQLi Followed by Server Error
Expected signal: Two sequential access log entries from the same source IP within a 5-minute window: one containing 'information_schema' and one resulting in an HTTP 500 response.
Unlock playbooks & atomic tests with Pro
Get the full detection package for CVE-2026-60137 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month