HomeWordPress vulnerabilitiesByteCoreStack
ByteCoreStack vulnerabilities
ByteCoreStack has 2 known vulnerabilities in this database. The most recent published record is dated 1 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 30+
- Latest version
- 1.2.4
- Last updated
- 24 Sep 2026
- Most recent
- 1 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Privilege escalation CVE-2026-103068 | High 8.8 | Up to 1.2.2 | Fixed in a later version (latest 1.2.4) | 6 d ago |
| Privilege escalation CVE-2026-19807 | High 8.8 | Up to 1.2.3 | Fixed in a later version (latest 1.2.4) | 6 d ago |
Read the published descriptions
- CVE-2026-103068, 1 Oct 2026
- Subscriber Privilege Escalation in ByteCoreStack – MCP Connector for AI Tools <= 1.2.2 versions. CVE record
- CVE-2026-19807, 1 Oct 2026
- 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. CVE record
What to do if you run ByteCoreStack
If you run ByteCoreStack, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new ByteCoreStack vulnerabilities
Free. We email you when a new vulnerability is published for ByteCoreStack, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.