🔥 CVE-2026-63030 深度独立研究：源码审计 · 二次发现 · 利用方案
🔥 高危漏洞深度独立研究 · CVSS ≥ 9.8
CVE-2026-63030 深度独立研究：源码审计 · 二次发现 · 利用方案
📊 4 来源🔍 源码审计🧪 PoC
NVD-LatestCISA-KEVPoC-in-GitHubVulhub
🔍 源码独立审计
对 （未定位到源码） 源码进行独立审计（置信度 60%）。
🧬 根因独立理解
<p><strong>摘要：</strong>CVE-2026-63030 是 WordPress 核心中一个由 REST API 批量端点路由混淆引发的严重漏洞，CVSS 评分为 9.8（Critical）。该漏洞影响 WordPress 6.9.0 至 6.9.4 以及 7.0.0 至 7.0.1 版本，攻击者可通过未认证的批量请求触发路由误派，并与 CVE-2026-60137（WP_Query 的 author__not_in 参数 SQL 注入）链式利用，最终实现数据库窃取、权限提升乃至远程代码执行。该漏洞已被 CISA 列入已知被利用漏洞目录（KEV），属于实质性威胁。</p> <h2>📌 漏洞概述</h2> <ul> <li><strong>CVE 编号：</strong>CVE-2026-63030</li> <li><strong>CVSS 评分：</strong>9.8（Critical）</li> <li><strong>影响版本：</strong>WordPress 6.9.0 – 6.9.4、7.0.0 – 7.0.1（已修复版本：6.9.5、7.0.2）</li> <li><strong>漏洞类型：</strong>解释冲突（Interpretation Conflict） / 路由混淆（Route Confusion），可链式触发 SQL 注入与远程代码执行</li> <li><strong>利用前提：</strong>无需认证，远程可利用</li> <li><strong>利用链：</strong>CVE-2026-63030（REST API 批量端点路由混淆） → CVE-2026-60137（WP_Query author__not_in SQL 注入） → 管理员权限获取 → RCE</li> </ul> <h2>🔬 漏洞根因分析</h2> <p>该漏洞的核心根因位于 WordPress REST API 的批量（Batch）端点实现中。REST 批量端点（<code>/batch/v1</code>）在默认情况下无需认证即可访问，其设计目的是在一个 HTTP 请求中同时执行多个子请求，以降低客户端与服务器之间的往返次数。为了确保安全性，每个子请求都应独立完成路由匹配、参数验证和权限检查。然而，在 <code>serve_batch_request_v1()</code> 函数的实现中，开发人员使用了两个平行的数组来管理子请求的处理信息：</p> <ul> <li><code>$matches</code>：存储每个子请求匹配到的路由处理函数（handler）；</li> <li><code>$validation</code>：存储每个子请求的校验结果（validation result）；</li> </ul> <p>理想情况下，这两个数组应按顺序一一对应，即第 N 个子请求的校验结果应与第 N 个子请求的处理函数绑定。但在具体实现中，当一个子请求的路径在调用 <code>wp_parse_url()</code> 时解析失败（例如包含非法 URL 字符、协议相对路径或异常编码），该子请求会被追加到 <code>$validation</code> 数组中，但不会追加到 <code>$matches</code> 数组中。这导致两个数组的下标发生错位——后续子请求的校验结果与之前某个子请求的处理函数被错误地配对，从而产生“路由混淆”。</p> <p>更具体地，攻击者可以构造一个包含多个子请求的批量请求，其中第一个子请求的 URL 故意解析失败，促使它被记录在校验数组中而不被记录在匹配数组中；随后的子请求则会被分派到一个与之不匹配的处理函数下执行。由于 WordPress 在批量处理时假设每个子请求已经过独立验证，因此不会对最终调度的 handler 重新进行权限检查或能力验证。攻击者借此可以绕过路由层面的安全限制，让一个原本仅允许特定权限级别的操作，在另一个 handler 的上下文中被非法触发。</p> <p>这一漏洞的实际危害并非孤立存在，而是与另一个核心漏洞 CVE-2026-60137 紧密相关。CVE-2026-60137 是 WordPress 的 WP_Query 类中 <code>author__not_in</code> 参数存在 SQL 注入漏洞。该参数用于排除指定作者的文章，但在较新版本的 WordPress 中，该参数被错误地并入 SQL 查询的 IN 子句时，未进行充分的类型强制转换与转义，导致恶意构造的值可以闭合 SQL 语法，形成注入点。然而，这个 SQL 注入点需要满足特定条件才能被触发，例如请求必须通过某些 REST API 端点进入，且权限检查
🛤️ 漏洞触发链路
🧪 PoC 复现
从 GitHub 公开仓库抓取的实际 PoC 代码（仓库）。
📋 代码元数据语言md来源Icex0/wp2shell-poc针对性⚠️ 疑似通用代码（未检测到 CVE 引用，仅供参考）依赖见代码注释/README用法详见代码注释中的使用说明
# wp2shell-poc
Independent proof-of-concept for the unauthenticated WordPress REST batch route-confusion
SQL injection associated with Searchlight Cyber's wp2shell advisory.
This repository is not Searchlight Cyber's official checker. `check` confirms the SQLi path,`read` demonstrates database read,
and `shell` opens a plugin-backed command shell either with
supplied administrator credentials or by first exercising the SQLi-to-admin bridge.
**Detection / IoCs:** Elastic Security Labs and Eye Security published detection guidance and indicators for this chain. See the [Elastic write-up](https://www.elastic.co/security-labs/wp2shell-wordpress-rce-detection-elastic-defend) and the [Eye Security defenders guide](https://labs.eye.security/wp2shell-defenders-guide/).
## Affected versions
Searchlight Cyber's advisory lists these wp2shell RCE exposure ranges:
|
Version range |Status ||------------- |------ ||<= 6.8.5 |Not affected ||6.9.0 – 6.9.4 |Affected ||7.0.0 – 7.0.1 |Affected |## How it works
The REST batch endpoint (`/batch/v1`) is unauthenticated and runs several sub-requests in one
call,
relying on each sub-request being validated and permission-checked on its own.
`serve_batch_request_v1()` builds two parallel arrays — `$matches` (the matched handler per
sub-request) and `$validation` (the validation result per sub-request) — then indexes both by
the same offset when dispatching. A sub-request whose path fails `wp_parse_url()` is appended to
`$validation` but not to `$matches`,
so the arrays fall out of step and a sub-request is
dispatched under a **different** sub-request's handler. That is the route confusion.
The PoC nests the primitive twice:
1. A `POST /wp/v2/posts` request that carries a `requests` body is dispatched under the batch
handler itself. Having been validated as a posts request,its `requests` list is never checked
against the batch schema,
so its sub-requests may use `GET` — the method allow-list is
bypassed.
2. Inside that inner batch,a `GET /wp/v2/posts/999999` item-route request carries posts collection
query params such as `author_exclude`,`orderby`,and `per_page`. The `999999` ID does not need
to exist;it is just an unlikely post ID used to match the item route,
whose schema does not
validate those collection-only params. The desync then dispatches the same request under posts
`get_items()`,where `author_exclude` maps to the `WP_Query` `author__not_in` query var,
which
the vulnerable build interpolates into SQL as a string.
The result is a boolean- and time-based blind SQL injection reachable pre-authentication. This PoC
also includes the UNION fake-post primitive used by the SQLi-to-admin chain.
The RCE path implemented here is:
1. Use UNION fake `wp_posts` rows to render attacker-controlled content through a posts collection.
The render bridge uses the `/wp/v2/posts/999999` item-route source — the same route the SQLi read
uses to reach `get_items()`.
2. Use that render to make WordPress create real oEmbed cache posts.
3. Recover those real cache post IDs through the SQLi.
4. In one poisoned batch request,
recast those IDs as a customizer changeset,navigation item,and
request hook shape.
5. Let the same request reach `POST /wp/v2/users`,creating a generated administrator.
6. Log in as that generated administrator and use plugin upload behavior to run a command.
Steps 1–5 are pre-authentication;
the command-execution step is authenticated admin plugin upload.
## Requirements
Python 3.8+ and the standard library. No third-party dependencies.
## Usage
Run it from the repository directory:
```
./wp2shell.py <command><url>
[options]
```
Or `pip install .` to get a `wp2shell` command on your `PATH`.
### check — non-destructive vulnerability check
Prints passive WordPress markers and public version hints first,then sends a benign batch marker
probe. A vulnerable batch implementation returns HTTP 207 with the route-confusion marker pattern
`parse_path_failed`,`block_cannot_read`,
and `rest_batch_not_allowed`.
The marker probe is based on the WordPress core fix. The malformed `///` request creates
`parse_path_failed`;a `/wp/v2/posts` request acts as a batch-allowed spacer;the
`/wp/v2/block-renderer/...` route is not batch-allowed but returns `block_cannot_read` if its
handler is reached anonymously;
`/batch/v1` gives `rest_batch_not_allowed`. On vulnerable builds
the parse error shifts the batch handler arrays out of step,so the spacer request is dispatched
under the block-renderer handler. Fixed builds keep the arrays aligned,so this exact all-three
pattern should not appear for the crafted probe.
By default,
`check` stops there and does not send an SQLi payload. Use `--confirm-sqli` when you
also want an active SQLi confirmation. The confirmation tries the UNION read primitive first and
falls back to paired timing probes if UNION reflection is unavailable.
The signals are independent: a version hint is only a hint,the marker pattern shows route
confusion,
and `--confirm-sqli` shows a payload reached the database. A WAF can block the payload,
so a failed confirmation doesn't prove the bug is absent.
```
./wp2shell.py check http://target
./wp2shell.py check targets.txt # scan every URL in the file
```
### read — extract data through SQL injection
```
./wp2shell.py read http://target # server fingerprint
./wp2shell.py read http://target --preset users # user logins and password hashes
./wp2shell.py read http://target --query "SELECT @@version"
```
By default extraction is `--technique auto`,
which tries the available methods in this order:
1. **union** — forges a fake `WP_Post` row via `UNION` and reads its title back from the REST
response as `||HEX(value)||`. The payload uses the same `/wp/v2/posts/999999` source route with
`orderby=none` and `per_page=500` so the fake row survives as a rendered post. One request per
value.
2. **error** — `EXTRACTVALUE`/`UPDATEXML` leak ~15 bytes per request,
when the target reflects
MySQL errors (e.g. `WP_DEBUG_DISPLAY` on).
3. **blind** — boolean binary search,~8 requests per character;reads the posts collection
`X-WP-Total` header as the true/false signal and needs no reflected value.
Force one with `--technique union|error|blind`. These read paths do not write database rows.
### shell — command execution
With `--user` and `--password`,
`shell` logs in with supplied administrator credentials and uses
WordPress plugin upload behavior.
Without credentials,`shell` first runs the pre-auth SQLi-to-admin bridge,logs in as the generated
administrator,
then uploads the plugin shell.
```
./wp2shell.py shell http://target --user admin --password '<recovered>' --cmd id
./wp2shell.py shell http://target --user admin --password '<recovered>' -i # interactive shell
./wp2shell.py shell http://target --cmd id # pre-auth bridge
./wp2shell.py shell http://target -i # pre-auth interactive
```
`shell` uploads a plugin webshell (locked behind a random path and a per-run token) and prints its
path. The uploaded webshell is removed automatically. When the pre-auth bridge creates an
administrator,
that generated account is removed automatically after the shell session finishes.
## Options
|Option |Applies to |Description ||------------------- |---------- |-------------------------------------------------------------------- ||`--proxy URL` |all |Route traffic through an HTTP proxy (for example,
Burp). ||`--timeout N` |all |Request timeout in seconds. ||`--sleep N` |check |Delay used by the timing fallback for `--confirm-sqli`. ||`--samples N` |check |Timing pairs used by the timing fallback for `--confirm-sqli`. ||`--confirm-sqli` |check |
Also send an active SQLi confirmation payload. ||`--preset` |read |`fingerprint` or `users`. ||`--technique` |read |`auto` (default),`union` (in-band,forges a fake post),`error` (in-band,needs visible DB errors),or `blind`. ||`--query` |read |
A scalar SQL expression to read. ||`--prefix` |read |Database table prefix (default `wp_`). ||`--max-length N` |read |Maximum characters read per value (default 128). ||`--user` / `--password` |shell |Optional admin credentials;omit both to use the pre-auth bridge. ||
`--cmd` |shell |Command to run (omit when using `-i`). ||`-i` / `--interactive` |shell |Open an interactive shell after deploying. |## Remediation
Update to WordPress 7.0.2,or 6.9.5 if the site is on the 6.9 branch. Until then,block both `/wp-json/batch/v1` and the `rest_route=/batch/v1` query parameter at
the edge,
or require authentication for the batch endpoint via the
`rest_pre_dispatch` filter.
## Legal
For authorized security testing only. Use it exclusively against systems you own or have explicit
written permission to test. No warranty is provided and no liability is accepted for misuse.
## References
- WordPress 7.0.2 release announcement — <https://wordpress.org/news/2026/07/wordpress-7-0-2-release/>
- Searchlight Cyber wp2shell advisory — <https://slcyber.io/research-center/wp2shell-pre-authentication-rce-in-wordpress-core/>- Hackify — wp2shell technical analysis — <https://hackify.nl/en/blog/wp2shell-wordpress-core-rce/>- sergiointel/wp2shell-poc SQLi-to-admin bridge — <https://github.com/sergiointel/wp2shell-poc>- Elastic Security Labs — wp2shell detection &
IoCs — <https://www.elastic.co/security-labs/wp2shell-wordpress-rce-detection-elastic-defend>- Eye Security — wp2shell defenders guide — <https://labs.eye.security/wp2shell-defenders-guide/>⚔️ EXP 利用代码
截至分析时，Exploit-DB 未收录该 CVE 的公开利用代码。可利用上述 PoC 进行验证，或关注 Exploit-DB 更新。
🕵️ 检测指纹
当前规则库未收录针对该 CVE 的专用检测规则。建议：
- 根据漏洞根因编写 Nuclei 检测模板
- 在 WAF/IDS 中配置针对漏洞特征的规则
- 关注漏洞指纹库更新
🤖 高危漏洞深度独立研究引擎生成 · 2026-08-02 12:03