Categories
CVE-2026-19807 high CVSS 8.8

Privilege Escalation in ByteCoreStack – MCP Connector for AI Tools (WordPress plugin) (CVE-2026-19807)

Summary

Vulnerability in ByteCoreStack – MCP Connector for AI Tools (WordPress plugin) (CVE-2026-19807). Successful exploitation can lead to full system takeover. Exploitable via wp_update_user_meta.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-19807 has been found in ByteCoreStack – MCP Connector for AI Tools (WordPress plugin).
Attackers can target a specific entry point like wp_update_user_meta over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ByteCoreStack – MCP Connector for AI Tools (WordPress plugin) CVE-2026-19807" on the vendor's site.

CVE-2026-19807 (ByteCoreStack – MCP Connector for AI Tools (WordPress plugin)) — CWE-269 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: wp_update_user_meta / execute_tool / map_meta_cap / read
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in ByteCoreStack – MCP Connector for AI Tools (WordPress plugin). Attackers reach the vulnerable code path via wp_update_user_meta.

📍 Affected scope

Check the vendor advisory for the affected versions of ByteCoreStack – MCP Connector for AI Tools (WordPress plugin). Attack surface: wp_update_user_meta / execute_tool / map_meta_cap / read.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで ByteCoreStack – MCP Connector for AI Tools (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details