CVE-2026-60137
WordPress Core SQL Injection
- Published17 Jul 2026
- Added to CISA KEV21 Jul 2026
- Remediation due4 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-60137 being actively exploited?
Yes. CVE-2026-60137 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 21 Jul 2026.
How severe is CVE-2026-60137?
CVE-2026-60137 has a CVSS 3.1 base score of 5.9, rated medium. EPSS estimates a 5.32% probability of exploitation.
Which products are affected by CVE-2026-60137?
Affected products include WordPress.
How do I fix CVE-2026-60137?
Upgrade affected software to a fixed version, for example WordPress 6.8.6 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-60137 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.