WordPress Core SQL Injection Vulnerability
WordPress — WordPress
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.
5.9
78.3%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- Jul 17, 2026
- Modified
- Oct 7, 2026
- Added to KEV
- Jul 21, 2026
- Federal patch due
- Aug 4, 2026
CISA 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.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2026-60137, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit — cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2026-60137 were found at last check. Absence here is not proof no exploit exists — see the references below for vendor advisories and write-ups.
References
How this class of flaw gets exploited
Frequently asked questions
What is CVE-2026-60137?
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 has a CVSS base score of 5.9 out of 10 (CVSS 3.1).
Is CVE-2026-60137 actively exploited in the wild?
Yes. CVE-2026-60137 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Jul 21, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2026-60137?
78.3% - meaning FIRST.org's EPSS model estimates a 78.3% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).
What type of vulnerability is CVE-2026-60137?
CVE-2026-60137 is classified under CWE-89 (CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')).
Cross-checked against
Impactr finds and proves whether CVE-2026-60137 — or flaws like it — are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.