CVE-2026-60137
WordPress Core SQL Injection Vulnerability
WordPress Core
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 21 July 2026. US federal agencies were required to remediate it by 4 August 2026.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 73.1%, which is higher than 99.4% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2026-60137 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2026-60137.
What does CVE-2026-60137 affect?
CVE-2026-60137 affects WordPress Core. 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.
How severe is CVE-2026-60137?
CVE-2026-60137 is rated MEDIUM with a CVSS base score of 5.9. EPSS puts the probability of exploitation in the next 30 days at 73.1%, higher than 99.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 4 August 2026.
How should organisations respond to CVE-2026-60137?
Apply the vendor patch for WordPress Core as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.