EUVD-2026-45279Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocate site with plugin feeding author__not_in
-
ExploitSend crafted parameter over HTTP
-
ExecutionInject SQL into WP_Query WHERE clause
-
ImpactExtract user hashes and secrets from database
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a plugin or theme on the target WordPress site to pass attacker-controlled input into the author__not_in parameter of WP_Query - this is the exact precondition stated in the description, and unmodified WordPress core does not expose that parameter to untrusted input by default. The affected site must run WordPress 6.8.x below 6.8.6, 6.9.x below 6.9.5, or 7.0.x below 7.0.2. The CVSS vector (PR:N/UI:N) indicates that, given such a vulnerable plugin/theme code path, no authentication or user interaction is needed and the request is network-reachable; the dependency on a non-default plugin/theme integration is the primary factor limiting real-world exploitation, and databases where the plugin passes only integer-cast values are not exposed. |
| Impact | The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:N, 9.1) portrays an unauthenticated, low-complexity, network-reachable flaw, and CISA SSVC agrees the technical impact is total and the flaw is automatable - signals that argue for high priority. However, these must be weighed against a critical conditional stated in the description: the parameter is only exploitable when a plugin or theme passes untrusted input to author__not_in, so default core WordPress is not directly attackable and the effective attack complexity is higher than AC:L implies. This is a genuine conflict between the raw CVSS/automatable signals and the real-world precondition, and it should be verified against the specific plugins/themes in use. SSVC exploitation status is 'none', EPSS was not provided, there is no KEV listing, and no public exploit was identified, so this currently reads as a serious latent flaw in a ubiquitous platform rather than an actively-exploited emergency - but the massive WordPress footprint plus 'automatable=yes' means it should be patched promptly. |
| Exploit ScenarioDerived | An attacker targets a WordPress site running a plugin whose front-end feature (for example a post-filtering or directory listing widget) passes a request parameter straight into WP_Query's author__not_in argument. The attacker submits a crafted value containing SQL syntax, causing a UNION- or boolean-based blind injection that extracts wp_users password hashes and secret keys from the database. Given CVSS AV:N/AC:L and SSVC automatable=yes the request can be delivered remotely without authentication, though no public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 17, 2026
SQL injection in WordPress core (6.8.x before 6.8.6, 6.9.x before 6.9.5, 7.0.x before 7.0.2) arises from improper sanitisation of the author__not_in parameter in WP_Query, allowing an attacker to inject SQL when a plugin or theme forwards untrusted input into that parameter. Reported by WPScan and rated CVSS 9.1, it can lead to full database disclosure on affected sites, but exploitation is not reachable through unmodified core alone - a vulnerable plugin or theme code path is required. No public exploit identified at time of analysis and it is not listed in CISA KEV, though CISA SSVC flags the technical impact as total and the flaw as automatable.
RemediationAI
Vendor-released patch: upgrade WordPress core to 6.8.6, 6.9.5, or 7.0.2 depending on your branch, as described in the WordPress 7.0.2 release announcement (https://wordpress.org/news/2026/07/wordpress-7-0-2-release/) and advisory GHSA-fpp7-x2x2-2mjf; sites with automatic minor-version updates enabled will typically receive the fix without action. Where immediate core patching is not possible, audit plugins and themes for any code that passes user-controlled data into WP_Query's author__not_in argument and cast those values to integers (for example wrapping input in array_map('intval', ...)) before the query, since this closes the specific injection path at the cost of a small code change. As a compensating control, a WAF rule that inspects request parameters for SQL metacharacters reaching author-exclusion query strings can reduce exposure, though it risks false positives and will not catch every plugin-specific parameter name; restricting or disabling untrusted plugins/themes that expose raw query arguments is the more reliable interim measure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic CWE-89 SQL injection in WP_Query, the central database query abstraction used throughout WordPress core, plugins, and themes to retrieve posts. The author__not_in argument is intended to accept an array of author IDs to exclude and is normally cast to integers before being folded into the generated SQL WHERE clause; in the affected builds this value is not properly sanitised, so a string containing SQL metacharacters is concatenated into the query. Because WP_Query queries execute against the wp_posts/wp_users schema via the shared $wpdb connection, a successful injection runs with the database privileges the WordPress site itself holds. The single affected CPE is cpe:2.3:a:wordpress:wordpress (all versions wildcard in the feed), with the concrete affected ranges enumerated by ENISA EUVD (EUVD-2026-45279).
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Unauthenticated network SQLi (PR:N) but requires a non-default vulnerable plugin/theme path so AC:H; enables data extraction (C:H) with limited write in a SELECT context (I:L), no availability impact.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: WPScan
Lifecycle Timeline
7DescriptionCVE.org
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.
Articles & Coverage 4
Executive ViewAI
A SQL injection vulnerability in WordPress core (CVE-2026-60137, CVSS 9.1) allows attackers to disclose entire databases when vulnerable plugins or themes forward untrusted input to WP_Query; no public exploit identified at time of analysis. This affects WordPress 6.8.x, 6.9.x, and 7.0.x sites, exposing customer data, credentials, and proprietary content to full disclosure.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
CISA KEV
EPSS
Vulnrichment
GitHub
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
Exploit-DB