Plugin-Mcp (>= 3.61.0, < 3.88.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/plugin-mcp--3.61.0--3.88.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 06 Oct 2026 18:48:00 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgImproper Access Control in Payload CMS MCP Pluginhttps://feed.craftedsignal.io/briefs/2026-10-payload-mcp-access-control/Tue, 06 Oct 2026 18:48:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-payload-mcp-access-control/An improper access control vulnerability (CVE-2026-105806) in the @payloadcms/plugin-mcp package allows authenticated users to manage API keys across accounts, facilitating privilege escalation and account takeover.The @payloadcms/plugin-mcp package for Payload CMS is affected by an improper access control vulnerability, tracked as CVE-2026-105806, impacting versions 3.61.0 through 3.87.9. This vulnerability allows an already authenticated user to interact with and manage Model Context Protocol (MCP) API keys belonging to accounts other than their own. By manipulating requests to the API key management endpoints, an attacker can hijack these keys, potentially leading to unauthorized access, further privilege escalation, and full account takeover within the Payload CMS environment. The issue stems from insufficient validation of ownership or permission boundaries during API key management operations. Defenders should prioritize patching, as this flaw directly undermines the security boundaries between users in a multi-tenant or collaborative CMS deployment.

Impact

The vulnerability allows unauthorized management of security credentials (API keys) across different user accounts within the same Payload CMS instance. If exploited, an attacker can gain control over administrative or higher-privileged API keys, leading to complete account takeover, exfiltration of sensitive CMS data, or unauthorized configuration changes. The impact is significant for organizations relying on the MCP plugin for automated workflows and integrations.

Recommendation

  • Upgrade the @payloadcms/plugin-mcp package to version 3.88.0 or later immediately to patch CVE-2026-105806.
  • If immediate patching is not feasible, disable the MCP plugin functionality until the upgrade is performed.
  • Audit logs for the API key management endpoints in Payload CMS to identify unauthorized access attempts or unusual patterns involving key manipulation from non-administrative users.
  • Restrict access to MCP API-key management interfaces to a highly limited set of trusted users until the software is updated.
]]>highadvisoryprivilege-escalationcmsweb-application