Is ByteCoreStack safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.3.0). As of 2026-11-04. 2 issues are on record for older versions; version 1.2.4 or newer fixes all of them that state a fix. Keep ByteCoreStack on the latest version (1.3.0) and remove it if you do not use it.

Which versions of ByteCoreStack are vulnerable?

Known issues on record (newest first): Privilege escalation (1.2.2 and older, fixed in 1.2.4); Privilege escalation (1.2.3 and older, fixed in 1.2.4). The full list with sources is on this page.

What is the latest version of ByteCoreStack?

1.3.0, according to wordpress.org (last updated 2026-10-24). It has 20+ active installs.

What should I do if my ByteCoreStack is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update bcs-mcp-manager). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · bcs-mcp-manager · data as of 2026-11-04

Is ByteCoreStack safe? Known vulnerabilities and latest version

Latest version: 1.3.0
Last updated: 2026-10-24
Active installs: 20+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

Connect Claude, ChatGPT and other AI clients to WordPress with MCP, OAuth 2.0, and 360 tools for content, WooCommerce and SEO. — by ByteCore Stack

What to do

Update to the latest version (1.3.0). Anything older than 1.2.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get bcs-mcp-manager --field=version shows what you run; wp plugin update bcs-mcp-manager updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 8.8 CVE-2026-103068 · published 2026-10-01

Privilege escalation in ByteCoreStack (1.2.2 and older)

Affected: 1.2.2 and older
Fixed in: 1.2.4
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Subscriber Privilege Escalation in ByteCoreStack – MCP Connector for AI Tools <= 1.2.2 versions.

NVD CVE-2026-103068 Patchstack advisory

high 8.8 CVE-2026-19807 · published 2026-10-01

Privilege escalation in ByteCoreStack (1.2.3 and older)

Affected: 1.2.3 and older
Fixed in: 1.2.4 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-19807 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-10-24 — latest release on wordpress.org (1.3.0).
2026-10-01 — Privilege escalation disclosed (CVE-2026-103068), fixed in 1.2.4.
2026-10-01 — Privilege escalation disclosed (CVE-2026-19807), fixed in 1.2.4.

Free. We check the CVE feeds every day and email you only when a new issue for ByteCoreStack (bcs-mcp-manager) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Privilege escalation (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/bcs-mcp-manager (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/bcs-mcp-manager"><img src="https://laskyr.com/plugins/bcs-mcp-manager/badge.svg" alt="ByteCoreStack vulnerability status"></a>

← Check another plugin · Free hacked-site scan