CVE-2026-60137: WordPress core SQL injection via WP_Query author__not_in

Exploited in the wild Medium 5.9 EPSS 5.3% WordPress core

WordPress 6.8 and later do not properly sanitise the author__not_in parameter of WP_Query, so SQL injection is possible when a plugin or theme passes untrusted input to it. On WordPress 6.9 and later it can be chained with the REST API batch-route confusion bug CVE-2026-63030 to reach remote code execution on default installs. Fixed in 7.0.2, 6.9.5 and 6.8.6 on 17 July 2026 (WordPress forced auto-updates); CISA added it to KEV on 21 July 2026.

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

  1. Check whether you run WordPress core and which version (commands below).
  2. Install the fixed version for your system: see “Patch it” below.
  3. No restart needed.
  4. If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
  5. Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Fixed in:

Am I affected?

wp core version --path=/var/www/html
dpkg -l wordpress | grep ^ii   # Debian package

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian
sudo apt update
sudo apt install --only-upgrade wordpress
Ubuntu
sudo apt update
sudo apt install --only-upgrade wordpress
RHEL, AlmaLinux, Rocky, Oracle
sudo dnf upgrade --refresh wordpress (EPEL)
Fedora
sudo dnf upgrade --refresh wordpress
SUSE / openSUSE
not packaged
Amazon Linux
not packaged: upstream
Arch Linux
sudo pacman -Syu
Alpine
not packaged
FreeBSD
pkg update && pkg upgrade wordpress
Built from source
wp core update --path=/var/www/html
wp core update-db --path=/var/www/html
# or Dashboard > Updates > Update Now

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

Fix status in Linux distributions

ReleasePackageStatusFixed version / advisory
Debian 12wordpressnot affected
Debian 13wordpressfixed6.8.6+dfsg1-0+deb13u1
Debian testingwordpressfixed7.0.2+dfsg1-1
Debian 13 (trixie)wordpressfixed6.8.6+dfsg1-0+deb13u1 (DSA-6399-1)

From the Debian security tracker, Ubuntu CVE tracker and Red Hat Security Data API, refreshed every few hours.

If you cannot patch yet

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.

https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-60137

Related vulnerabilities

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.