CVE-2026-60137: WordPress < 7.0.2 - Facilitated SQL Injection via author__not_in in WP_Query
Noroxi assessment
Priority: This week (action score 60/100)
- CISA has confirmed exploitation in the wild (Jul 21, 2026). Remediation deadline for US federal agencies: Aug 4, 2026.
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
- Probability of exploitation in the next 30 days: 5.3% (FIRST EPSS); higher than 92.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: WordPress WordPress 6.8.6, 6.9.5, 7.0.2.
Don’t wait for the next maintenance window. Upgrade to WordPress WordPress 6.8.6, 6.9.5, 7.0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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.
- Published
- Jul 17, 2026
- Updated
- Oct 8, 2026
- EPSS
- 5.3% · 92th percentile
- CWE
- CWE-89
Report tools
Action score
60
This week
Don’t wait for the next maintenance window.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 2 / 30 · 5.3%
- Ready-made attack tool
- 5 / 60 · floor: at least 60
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WPScan
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Jul 21, 2026. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Aug 4, 2026.
Is WordPress on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wordpress | wordpress | cpe:2.3:a:wordpress:wordpress |
Using wordpress? Add it to your stack and be the first to know about CVEs like this one. (WordPress)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wordpress wordpress6.8 and later · before 6.8.6
- wordpress wordpress6.9 and later · before 6.9.5
- wordpress wordpress7.0 and later · before 7.0.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.
WordPress WordPress
- 6.8.0 and later · before 6.8.6affected · semver
- 6.9.0 and later · before 6.9.5affected · semver
- 7.0.0 and later · before 7.0.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | wordpress | before 6.8.6+dfsg1-0+deb13u1 | 6.8.6+dfsg1-0+deb13u1 |
| Debian:14 | wordpress | before 7.0.2+dfsg1-1 | 7.0.2+dfsg1-1 |
Same product
wordpress: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-87902An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the KEV91Now
- CVE-2026-63030WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code ExecutionKEV72This week
- CVE-2019-8942WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an a60This week
Published before and after this one in the same product
- ← EarlierCVE-2025-58246Sep 23, 2025 · WordPress <= 6.8.2 - (Contributor+) Sensitive Data Exposure Vulnerability17Monitor
- ← EarlierCVE-2025-58674Sep 23, 2025 · WordPress <= 6.8.2 - (Author+) Cross Site Scripting (XSS) Vulnerability23Monitor
- Later →CVE-2026-64638Aug 7, 2026 · WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen.35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| WordPress WordPress | 6.8.6 | Vendor (CNA) |
| WordPress WordPress | 6.9.5 | Vendor (CNA) |
| WordPress WordPress | 7.0.2 | Vendor (CNA) |
| debian:wordpress | 6.8.6+dfsg1-0+deb13u1 · Debian:13 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×2
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×10
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | auxiliary/scanner/http/wordpress_wp2shell_sqliWordPress Core wp2shell Unauthenticated SQL Injection via REST Batch Route Confusionauxiliary | 2026-07-17 |
| Metasploit module | exploit/multi/http/wp_batch_desync_rceWordPress WP2Shell REST API Batch Route Confusion SQLi to RCEexploit | 2026-07-17 |
| Nuclei detection template | Nuclei template CVE-2026-63030 | — |
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-18 |
| Proof-of-concept repository on GitHub | stars:10 | 2026-07-18 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-21 |
| Proof-of-concept repository on GitHub | stars:4 | 2026-07-21 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-26 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-27 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-01 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-03 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-05 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-1 d
- Published
- First PoCsame day
- CISA KEV+3 d
- TodayOct 31, 2026+105 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- TF1Tfinder
- dtrofinder
- haongofinder
- WordPress Security Teamcoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.