{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-19807 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-19807 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19807 is a high-severity vulnerability in ByteCoreStack – MCP Connector for AI Tools, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-19807 and fix it if it is affected.\n\nWhat it is: CVE-2026-19807 is a high-severity vulnerability in ByteCoreStack – MCP Connector for AI Tools, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-19807 in the wild and no public exploit code.\n\nAffected product: ByteCoreStack – MCP Connector for AI Tools. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-19807/ (Markdown: https://insights.sbomify.com/CVE-2026-19807/index.md)","id":"CVE-2026-19807","markdown":"https://insights.sbomify.com/CVE-2026-19807/index.md","name":"CVE-2026-19807","record":{"aliases":["GHSA-qwvr-5fhh-47xh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can escalate to Administrator by updating their own user meta capabilities via the MCP tool due to insufficient validation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"ByteCoreStack \u003c= 1.2.3 - Authenticated (Subscriber+) Privilege Escalation via wp_update_user_meta MCP Tool","id":"CVE-2026-19807","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":13,"next":{"headline":"Cross-Site Scripting (XSS) in Symantec Endpoint Detection and Response Console","id":"CVE-2026-19810"},"packages":[],"prev":{"headline":"Auth bypass in Support Genix – Helpdesk, AI Chatbot, Knowledge Base \u0026 Customer Support Ticketing System","id":"CVE-2026-19806"},"products":["ByteCoreStack – MCP Connector for AI Tools"],"published":"2026-10-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-03","vendors":["bytecorestack"]},"summary":"Authenticated subscribers can escalate to Administrator by updating their own user meta capabilities via the MCP tool due to insufficient validation.","url":"https://insights.sbomify.com/CVE-2026-19807/"}