ByteCoreStack – MCP Connector for AI Tools
ByteCoreStack – MCP Connector for AI Tools (bcs-mcp-manager) is a WordPress plugin with 1 published CVE record in this archive. The latest tracked vulnerability was published Oct 01, 2026; the highest published CVSS base score is 8.8.
bcs-mcp-managerThis measures remediation-data coverage in this archive. It is not a claim that the plugin is vulnerability-free or insecure.
CVE-2026-19807: ByteCoreStack – MCP Connector for AI Tools: Privilege escalation or authentication bypass
The ByteCoreStack – MCP Connector for AI Tools plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.2.3 This is due to the `wp_update_user_meta` MCP tool in `execute_tool` gating writes solely with `current_user_can('edit_user', $uid)` — a check that WordPress core's `map_meta_cap` resolves to the `read` primitive when the target user ID matches the caller's own — while enforcing an incomplete meta key blocklist that covers only `user_pass`, `user_activation_key`, and `session_tokens`, leaving the `wp_capabilities` and `wp_user_level` meta keys entirely unprotected. This makes it possible for authenticated attackers with Subscriber-level access and above to elevate their privileges to Administrator by issuing a `wp_update_user_meta` call over the MCP JSON-RPC endpoint with `key=wp_capabilities` and an arbitrary role array such as `{'administrator': true}` targeting their own user ID, causing WordPress to load that account as an Administrator on the next request. The official changelog confirms a matching fix in 1.2.4.
| Safe version |
|
||
|---|---|---|---|
| Oct 01, 2026 |
CVE-2026-19807
ByteCoreStack – MCP Connector for AI Tools: Privilege escalation or authentication bypass
The ByteCoreStack – MCP Connector for AI Tools plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.2.3 This is due to the `wp_update_user_meta` MCP tool in `execute_tool` gating writes solely with `current_user_can('edit_user', $uid)` — a check that WordPress core's `map_meta_cap` resolves to the `read` primitive when the target user ID matches the caller's own — while enforcing an incomplete meta key blocklist that covers only `user_pass`, `user_activation_key`, and `session_tokens`, leaving the `wp_capabilities` and `wp_user_level` meta keys entirely unprotected. This makes it possible for authenticated attackers with Subscriber-level access and above to elevate their privileges to Administrator by issuing a `wp_update_user_meta` call over the MCP JSON-RPC endpoint with `key=wp_capabilities` and an arbitrary role array such as `{'administrator': true}` targeting their own user ID, causing WordPress to load that account as an Administrator on the next request. The official changelog confirms a matching fix in 1.2.4.
|
1.2.4 |
CVE8.8
NVDPending
|