CVE-2026-63030Known exploitationPublic exploitNetwork attack vector

Unauthenticated code execution via REST batch route confusion

Published Jul 17, 2026 · Updated Jul 17, 2026

Interpretation conflict in WordPress 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1 allows remote attackers to execute code via REST requests. After a subrequest path fails to parse, the batch handler loses synchronization between its validation and handler tables and dispatches a later subrequest through a handler for which it was not validated. No authentication or plugin is required, but exploitation chains the confusion with CVE-2026-60137 to reach SQL injection and then server-side code execution.

CVSS severity9.8
Critical
EPSS probability97.27%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Interpretation conflict in WordPress 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1 allows remote attackers to execute code via REST requests. After a subrequest path fails to parse, the batch handler loses synchronization between its validation and handler tables and dispatches a later subrequest through a handler for which it was not validated. No authentication or plugin is required, but exploitation chains the confusion with CVE-2026-60137 to reach SQL injection and then server-side code execution.

The record

CVE
CVE-2026-63030
Published
Jul 17, 2026
Updated
Jul 17, 2026
Vendor
WordPress.org
Product
WordPress
Classifications
CWE-436, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 17, 2026Record updatedLatest update available in the CVE record.
  3. Jul 21, 2026Exploitation reportedCISA Known Exploited Vulnerabilities Catalog listing

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.9.0 <6.9.5
  2. Affected versionversion=7.0.0 <7.0.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WordPress.org · WordPressversion=6.9.0 <6.9.5; version=7.0.0 <7.0.2

Published CVSS scores

9.8WPScanCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.5CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-436Interpretation Conflict
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo