GHSA-2q76-m6w6-qgc6: Npm/@payloadcms/plugin-mcp vulnerability
Impact Under certain conditions, an authenticated user could manage MCP API keys outside their intended account allowing an attacker to escalate privileges through account takeover.
Applications that do not use @payloadcms/plugin-mcp are not affected.
Patches Users should upgrade to @payloadcms/plugin-mcp version 3.88.0 or later.
Workarounds Upgrading is recommended. Until then, disable the MCP plugin or restrict MCP API-key management to trusted users.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@payloadcms/plugin-mcpto a version that resolves this vulnerability.Fixed in 3.88.0 - Upgrade
Upgrade
@payloadcms/plugin-mcpto a version that resolves this vulnerability.Fixed in 3.88.0 - Configuration
Disable the MCP plugin until upgrading.
@payloadcms/plugin-mcp MCP plugin = disabled - Compensating control
Restrict MCP API-key management to trusted users until upgrading.
Event History
Frequently Asked Questions
Which deployments are affected?
Only applications that use @payloadcms/plugin-mcp are affected. Applications that do not use this plugin are not affected.
What access does an attacker need?
Exploitation requires an authenticated user under certain conditions. The issue can allow that user to manage MCP API keys outside their intended account and escalate privileges through account takeover.
What version fixes the issue?
Upgrade @payloadcms/plugin-mcp to version 3.88.0 or later.
What can we do if we cannot upgrade immediately?
Disable the MCP plugin, or restrict MCP API-key management to trusted users until an upgrade can be performed.