CVE-2026-63030: WordPress REST API batch-route confusion leading to RCE

Exploited in the wild Critical 9.8 EPSS 10.6% WordPress core

WordPress 6.9 and later have a REST API batch endpoint route confusion flaw; combined with the author__not_in SQL injection (CVE-2026-60137) it lets an unauthenticated attacker perform SQL injection and achieve remote code execution on default installations. WordPress fixed both in 7.0.2 and 6.9.5 on 17 July 2026 and forced auto-updates because of the severity. CISA added it to KEV on 21 July 2026.

CVE-2026-63030CVE identifier
9.8CVSS 3.1 base score (critical)
2026-07-21added to CISA's exploited list (US federal deadline 2026-07-24)
10.6%EPSS: chance of exploitation in the next 30 days (higher than 96% of CVEs)
2026-07-17published

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

What to do now

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

Affected and fixed versions

Affected:

WordPress 6.9.0 through 6.9.4
WordPress 7.0.0 through 7.0.1
WordPress 7.1 beta1

Fixed in:

WordPress 7.0.2
WordPress 6.9.5
WordPress 7.1 beta2

Am I affected?

wp core version --path=/var/www/html

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

Release	Package	Status	Fixed version / advisory
Debian 12	`wordpress`	not affected
Debian 13	`wordpress`	not affected
Debian testing	`wordpress`	fixed	`7.0.2+dfsg1-1`

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

If you cannot patch yet

WordPress 6.8 and older are not affected by this flaw (6.8 is still affected by CVE-2026-60137). Debian's packaged versions are not affected.

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-63030

Related vulnerabilities

CVE-2026-60137

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.