CVE DatabaseCVE-2026-60137
한국어 권고문 →
CVE-2026-601375.9/MEDIUMCISA KEVCWE-89

WordPress WP_Query 'author__not_in' Parameter SQL Injection Vulnerability (CVE-2026-60137)

Affected Vendors
wordpress
Affected Components
wordpress
Published Date
2026-07-17

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

WordPress core versions 6.8.x (before 6.8.6), 6.9.x (before 6.9.5), and 7.0.x (before 7.0.2)

Impact

Successful exploitation allows remote attackers to execute arbitrary SQL commands and retrieve sensitive database information when a plugin or theme passes untrusted input to the 'author__not_in' parameter of WP_Query.

Mitigation

Immediately upgrade WordPress core to the patched versions (6.8.6, 6.9.5, or 7.0.2) and apply WAF filtering rules.

Affected Products & Version Scope

WordPress core versions 6.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Upgrade WordPress Core

Apply the official security updates immediately.

  • WordPress 7.0.x: Upgrade to 7.0.2 or higher
  • WordPress 6.9.x: Upgrade to 6.9.5 or higher
  • WordPress 6.8.x: Upgrade to 6.8.6 or higher

Using WP-CLI, you can update your installation with the following command:

bash
wp core update --version=7.0.2

2. Temporary Mitigation (WAF Rule)

If immediate patching is not possible, deploy a Web Application Firewall (WAF) rule to block non-numeric values in the author__not_in parameter.

ModSecurity Rule Example:

apache
SecRule ARGS:author__not_in "[^0-9,]" \
    "id:1000001,\
    phase:2,\
    deny,\
    status:400,\
    log,\
    msg:'CVE-2026-60137: SQLi Attempt in author__not_in parameter'"

3. Developer Remediation (Plugins & Themes)

Ensure all inputs passed to WP_Query parameters are strictly sanitized and type-cast to integers.

php
// Vulnerable Implementation
$args = [
    'author__not_in' => $_GET['exclude_authors']
];
$query = new WP_Query($args);

// Secure Implementation
$exclude_authors = isset($_GET['exclude_authors']) ? array_map('intval', (array)$_GET['exclude_authors']) :;
$args = [
    'author__not_in' => $exclude_authors
];
$query = new WP_Query($args);
Recommended Security Control & Mitigation Partner
Cloudflare Enterprise & Pro WAF
Due to active in-the-wild exploitation, immediately update your WordPress installations to the latest patched versions (7.0.2, 6.9.5, or 6.8.6).

Block Exploits Instantly with Managed Virtual Patching Rules

Can't patch production immediately? Deploy managed WAF rules at the edge to intercept RCE, SQLi, and deserialization payloads before they hit your origin server.

3-min setup · Automated Zero-Day Managed Rules
Practice Exploiting & Patching This Web Vulnerability in an Interactive Lab
Launch Hands-On Security Lab

Technical Root Cause & Exploitation Mechanics

This vulnerability (CVE-2026-60137) exists in the WP_Query class of WordPress core due to insufficient sanitization and type-casting of the author__not_in parameter.

While WordPress core does not directly expose this parameter to untrusted user input, many third-party plugins and themes pass raw HTTP request parameters (e.g., from $_GET or $_POST) directly into WP_Query arguments. An attacker can exploit this behavior by injecting malicious SQL payloads into the parameter, leading to SQL Injection (SQLi). This can be leveraged to extract sensitive data from the database, including user password hashes and session tokens.

This vulnerability is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and has an EPSS score of 0.94, indicating active exploitation in the wild and requiring immediate remediation.

Official Vendor Advisories & References

NVD Original English Description

WordPress 6.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2 does not properly sanitise the author__not_in parameter of WP_Query, which could allow SQL Injection when a plugin or theme passes untrusted input to the parameter.

SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed: