Actively exploited in the wild
WordPress Core SQL Injection Vulnerability
WordPress - Core · Listed in the CISA KEV since 2026-07-21. This indicates confirmed attacks in production environments.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CVE-2026-60137
MediumCVSS 5.9KEVExploitation Probability (EPSS)
Very high risk100th percentile - higher than 100% of all known CVEs
Summary
WordPress versions 6.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2 fail to properly sanitize the author__not_in parameter of WP_Query. This could allow SQL Injection when a plugin or theme passes untrusted input to this parameter.
Risk Assessment
An attacker could exploit this vulnerability to execute unauthorized SQL queries, potentially leading to data leakage, modification, or full compromise of the WordPress database.
Recommendation
Immediately update WordPress to version 6.8.6, 6.9.5, or 7.0.2 depending on your branch. Additionally, audit plugins and themes for passing untrusted data to the author__not_in parameter.
Other vulnerabilities in WordPress
See all- CVE-2012-6707High
WordPress through version 4.8.2 uses a weak MD5-based password hashing algorithm, making it easier for attackers to determine cleartext values by leveraging access to the hash values.
- CVE-2017-9066High
In WordPress before version 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF vulnerability.
- CVE-2017-9065High
In WordPress before version 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API.
- CVE-2017-9064High
In WordPress before version 4.7.5, a Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog because a nonce is not required for updating credentials.
- CVE-2017-9062High
In WordPress before version 4.7.5, there is improper handling of post meta data values in the XML-RPC API.
- CVE-2016-6896High
A directory traversal vulnerability in the wp_ajax_update_plugin function in WordPress 4.5.3 allows remote authenticated users to cause a denial of service or read certain text files via a .. (dot dot) in the plugin parameter to wp-admin/admin-ajax.php.
- CVE-2017-5489High
The CSRF vulnerability in WordPress before version 4.7.1 allows remote attackers to hijack the authentication of unspecified victims via vectors involving Flash file uploads.
- CVE-2016-4029High
WordPress before 4.5 does not consider octal and hexadecimal IP address formats when determining an intranet address, which allows remote attackers to bypass an intended SSRF protection mechanism via a crafted address.
- CVE-2016-5839High
WordPress versions before 4.5.3 allow remote attackers to bypass the sanitize_file_name protection mechanism via unspecified vectors.
- CVE-2016-5838High
WordPress before 4.5.3 allows remote attackers to bypass intended password-change restrictions by leveraging knowledge of a cookie.
Original NVD description (English source)
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.