CVE-2026-60137: WordPress < 7.0.2 - Facilitated SQL Injection via author__not_in in WP_Query
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.
Security readout for executives and security teams
Plain-English summary
A WordPress core flaw can let attackers inject database queries if a plugin or theme passes untrusted input into WP_Query's author__not_in filter. Affected versions are 6.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2. CISA KEV listing makes this urgent for public WordPress sites.
Executive priority
Treat as emergency patching for exposed WordPress assets. The issue is critical, unauthenticated, and listed by CISA as known exploited. Business risk is highest for public sites handling customer data, publishing workflows, or privileged content.
Technical view
CVE-2026-60137 is CWE-89 SQL injection in WordPress WP_Query handling of author__not_in. The flaw is reachable when extension code supplies untrusted data to that parameter. The CVSS 3.1 score is 9.1, network exploitable, low complexity, unauthenticated, with high confidentiality and integrity impact.
Likely exposure
Internet-facing WordPress installations on affected branches are the main concern, especially sites with plugins or themes that map user-controlled request data into WP_Query author__not_in. The source bundle does not identify specific vulnerable plugins or themes.
Exploitation context
CISA KEV status indicates known exploitation. The provided sources do not include exploit mechanics, payloads, campaign details, or affected extension names, so exploitation scope should be treated as confirmed but not fully characterized here.
Researcher notes
The core bug depends on an extension or theme passing untrusted input into author__not_in. Analysis should focus on data-flow from request parameters to WP_Query construction. The bundle confirms fixed version ranges but does not provide extension-specific exposure or exploit artifacts.
Mitigation direction
Update WordPress 6.8.x to 6.8.6 or later.
Update WordPress 6.9.x to 6.9.5 or later.
Update WordPress 7.0.x to 7.0.2 or later.
Review vendor advisory and release notes for operational guidance.
Prioritize externally reachable and high-value WordPress sites first.
Validation and detection
Inventory WordPress core versions across production and staging.
Confirm no site remains on affected pre-fix versions.
Review plugins and themes using WP_Query author__not_in with user input.
Check access and database error logs for suspicious author filtering activity.
Validate backups before updates and confirm site function afterward.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.