CVE-2026-19807: ByteCoreStack (WordPress plugin) · Improper Privilege Management
Affects ByteCoreStack (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bytecorestackByteCoreStack – MCP Connector for AI Tools | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the MCP Connector for AI Tools plugin and limit user roles to trusted users only. Monitor for unusual privilege changes and consider disabling or removing the plugin if possible.
Description
ByteCoreStack – MCP Connector for AI Tools plugin for WordPress versions up to 1.2.3 contains a privilege escalation vulnerability. Authenticated users with Subscriber-level access or higher can exploit improper privilege management in the wp_update_user_meta MCP tool to elevate their privileges to Administrator by modifying unprotected meta keys such as wp_capabilities. This vulnerability arises from insufficient gating of meta key writes and an incomplete meta key blocklist.
References
- wordfence.com/threat-intel/vulnerabilities/id/ac09bf3e-49cf-4f11-92ba-d1fbf6f587d7?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.2.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.2.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.2.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.2.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.2.0/includes/OAuth/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.1.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.1.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.1.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.1.0/includes/MCP/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bcs-mcp-manager/tags/1.1.0/includes/OAuth/Server.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&new=3711909%40bcs-mcp-manager%2Ftags%2F1.2.4&old=3711721%40bcs-mcp-manager%2Ftags%2F1.2.3 (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3711908/bcs-mcp-manager/trunk/includes/MCP/Server.php (opens in a new tab)