WordPress Core 6.9 — 7.0.1 - Remote Code Execution via REST API Batch Request Route Confusion
CVE-2026-63030Published · Updated Action summary
Affected: <7.0.2Update to 6.9.5 or 7.0.2 or newer
Fixed versions are per release branch: update to the fix for the branch you run.
All remediation stepsOn this page3
Overview
- Advisory ID
- CVE-2026-63030
- Product
- WordPress wordpress
- Affected
- <7.0.2
- Fixed in
- 6.9.5, 7.0.2
- Required access
- No account needed
- Published
- · updated
- Credit
- Adam Kues
- Source
- Wordfence Intelligence
- Affected< 7.0.2
- Patched in6.9.5 / 7.0.2
Update to 6.9.5 / 7.0.2 or newer.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
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.
Not sure which version you run? Run a passive check — it reads public files only.
Remediation & mitigations
- Update to one of the following versions, or a newer patched version: 6.9.5, 7.0.2
- Because this CVE is listed in CISA KEV, review the site for signs of compromise: unknown administrator accounts, new PHP files under wp-content/uploads, and unexpected redirects.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
References & provenance
Proof-of-concept & detection
This CVE is listed in CISA KEV. VulnCrest does not publish proof-of-concept code for KEV-listed vulnerabilities.
- UnreviewedGitHubSenanfurkan/wordpress-cve-2026-63030
- UnreviewedGitHubtcyph3r/wp2shell-cve-2026-63030-root-cause
- UnreviewedGitHubdinosn/wp2shell-lab
- UnreviewedGitHub47Cid/wp2shell-lab
- UnreviewedGitHubekomsSavior/wp2shell
- UnreviewedGitHubNULL200OK/WP2Shell
- UnreviewedGitHubkulichr/wp2shell
- UnreviewedGitHubCybersecSpirit/CVE-2026-63030
- UnreviewedGitHub4minx/CVE-2026-63030
- UnreviewedGitHubmverschu/CVE-2026-63030
- UnreviewedGitHub0xsha/wp2shell
- UnreviewedGitHubJ4ck3LSyN-Gen2/CVE-2026-63030-wp2r00t
- UnreviewedGitHubgbrsh/CVE-2026-63030
- UnreviewedGitHubashrafzaryouh/CVE-2026-63030
- UnreviewedGitHubmrx-arafat/CVE-2026-63030-POC
- UnreviewedGitHub0xWhoknows/wp2shell
- UnreviewedGitHubzi3lak/wp2shell_scanner
- UnreviewedGitHubsecurelayer7/WordPresShell
- UnreviewedGitHubfullhunt/wp2shell-scan
- UnreviewedGitHubChiefYoru/CVE-2026-63030_PoC
- UnreviewedGitHubown2pwn-fr/wp2shell-detect
- UnreviewedGitHubc0gnit00/Wp2Shell
- UnreviewedGitHubIcex0/wp2shell-poc
- UnreviewedGitHubattackercan/wp2shell-poc2
- UnreviewedGitHubZephrFish/wp2shell-scanner
Third-party code, not reviewed by VulnCrest. Fake PoC repositories regularly contain malware. Read the code before running anything, and only run it against a lab you own.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity critical, CVSS 9.8
Record last updated
Sources & licenses
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- KEV status
- CISA Known Exploited Vulnerabilities catalog (CC0 1.0).
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.