CVE-2026-63030

WordPress Core 6.9 - 7.0.1 - Remote Code Execution via REST API Batch Request Route Confusion

2026-07-17 00:00

Strategic Overview

Status: Patched in 6.9.5
Affected Core: WordPress 7.0
Affected Version: 6.9 – < 7.0.2 · 2 branches
CVSS: 9.8Critical
Weakness type: CWE-670 · Always-Incorrect Control Flow Implementation
CVE: CVE-2026-63030

At a glance

CVE-2026-63030 is a critical-severity Always-Incorrect Control Flow Implementation vulnerability in the WordPress 7.0 WordPress release line, affecting 6.9 – < 7.0.2 · 2 branches. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.9.5; sites on affected versions should update now. Disclosed July 2026, reported by Adam Kues.

Vulnerability Overview

WordPress Core is vulnerable to Remote Code Execution in all versions 6.9 to 7.0.1 via the REST API batch request endpoint (/wp-json/batch/v1). This is due to a route/validation desynchronization that allows a validated sub-request to be dispatched to an unintended callback, bypassing the allow_batch restriction, with attacker-controlled parameters and the target route's input sanitization bypassed, which can be chained with SQL Injection. This may make it possible for attackers to execute code on the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-670: Always-Incorrect Control Flow Implementation

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.

Remediation

Update to one of the following versions, or a newer patched version: 6.9.5, 7.0.2

How does WordSec protect against this?

The fix is the thing that ends this: updating to 6.9.5 is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-63030 https://www.wordfence.com/threat-intel/vulnerabilities/id/1ba55302-b38f-4932-bbba-cdd517380ad7 https://nvd.nist.gov/vuln/detail/CVE-2026-63030

Related records

Other vulnerabilities in WordPress 7.0

CVSS Vector

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/