WordPress up to 6.9.4/7.0.1 REST API Batch Endpoint interpretation conflict
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 5.29 |
Summary
A vulnerability identified as critical has been detected in WordPress up to 6.9.4/7.0.1. This impacts an unknown function of the component REST API Batch Endpoint. This manipulation causes interpretation conflict. This vulnerability is tracked as CVE-2026-63030. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical was found in WordPress up to 6.9.4/7.0.1. Affected by this vulnerability is some unknown functionality of the component REST API Batch Endpoint. The manipulation with an unknown input leads to a interpretation conflict vulnerability. The CWE definition for the vulnerability is CWE-436. Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-63030 since 07/17/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/18/2026).
Upgrading to version 6.9.5 or 7.0.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-45280). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Interpretation conflictCWE: CWE-436
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: WordPress 6.9.5/7.0.2
Timeline
07/17/2026 Advisory disclosed07/17/2026 CVE reserved
07/17/2026 VulDB entry created
07/18/2026 VulDB entry last update
Sources
Product: wordpress.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-63030 (🔒)
GCVE (CVE): GCVE-0-2026-63030
GCVE (VulDB): GCVE-100-379927
EUVD: 🔒
Entry
Created: 07/17/2026 21:52Updated: 07/18/2026 00:50
Changes: 07/17/2026 21:52 (53), 07/18/2026 00:50 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.