CVE-2026-105868: payloadcms payload · Unrestricted File Upload
Affects payloadcms payloadSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 4.0.0-canary.34 or 3.90.0 soon.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.0-canary.34, 3.90.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/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 payloadcms/payload to 4.0.0-canary.34 or 3.90.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| payloadcmspayload | Affected
| Fixed in
|
| payloadcmspayload | 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 Payload CMS to version 3.90.0 or later, or to canary version 4.0.0-canary.34 or later, where this vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.
Description
Payload CMS versions before 3.90.0 and canary versions before 4.0.0-canary.34 have a vulnerability allowing local upload configurations that accept XML files to store XML files and stylesheets that execute JavaScript in the Payload origin when opened by a logged-in user. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.