CVE-2026-105806: payloadcms payload · Missing Authorization
Affects payloadcms payloadSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 3.88.0 soon.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.88.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade payload and plugin-mcp and payloadcms/payload to 3.88.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| payloadcmspayload | Affected
| Fixed in
|
| @payloadcmsplugin-mcp | Affected
| Fixed in
|
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to version 3.88.0 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.
Description
### 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.