# CVE-2026-60137 — WordPress

> As of 2026-07-18, CVE-2026-60137 is a MEDIUM-severity vulnerability in WordPress, CVSS v3.1 5.9. Threadlinqs Intelligence links 4 tracked threat campaigns to CVE-2026-60137, most recently “AI-Agent-Driven Offensive Operation: Mass Cryptocurrency Wallet and Credential Compromise via Autonomous AI Coding Agents”.

**Last updated:** 2026-07-18

## 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.

The record classifies CVE-2026-60137 under weakness class [CWE-89](https://cwe.mitre.org/data/definitions/89.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 58 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.9 — MEDIUM (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-17, last modified 2026-07-18

## Is CVE-2026-60137 being exploited?

No public exploitation evidence for CVE-2026-60137 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-07-18. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

## Affected products and versions

- **WordPress**: WordPress

## How to fix CVE-2026-60137

No vendor patch reference has been recorded for CVE-2026-60137 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-60137

4 tracked threats in the Threadlinqs corpus reference CVE-2026-60137, either in the campaign’s CVE list or as an indicator on the campaign record.

- [AI-Agent-Driven Offensive Operation: Mass Cryptocurrency Wallet and Credential Compromise via Autonomous AI Coding Agents](https://intel.threadlinqs.com/threat/TL-2026-2070) — CRITICAL · 2026-08-19
- [wp2shell RCE Chain in WordPress Core (CVE-2026-60137, CVE-2026-63030) — Emergency Patch Released](https://intel.threadlinqs.com/threat/TL-2026-1465) — CRITICAL · 2026-07-18
- [wp2shell: WordPress Core REST API Batch-Route Confusion Chained with author__not_in SQL Injection (CVE-2026-63030 / CVE-2026-60137) Yields Unauthenticated Pre-Auth RCE](https://intel.threadlinqs.com/threat/TL-2026-1463) — CRITICAL · 2026-07-17
- [CVE-2026-63030 (wp2shell): Unauthenticated Remote Code Execution in WordPress Core REST API Batch Endpoint via Chained SQL Injection (CVE-2026-60137)](https://intel.threadlinqs.com/threat/TL-2026-1464) — CRITICAL · 2026-07-17

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-07-18. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [wordpress.org — release notes](https://wordpress.org/news/2026/07/wordpress-7-0-2-release/)

**Technical analysis**

- [github.com — vdb entry](https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-fpp7-x2x2-2mjf)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-60137
Full detection coverage and IOCs for threats exploiting CVE-2026-60137 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp