Skip to main content
VulnerabilityPublished

CVE-2026-105862: payloadcms payload · Cross-site Scripting

Affects payloadcms payloadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 4.0.0-canary.34 or 3.90.0 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% 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:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
payloadcmspayloadAffected
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 4.0.0-canary.34
payloadcmspayloadAffected
  • <3.90.0
Fixed in
  • 3.90.0
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threatsAffected
  • <3.90.0
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 3.90.0
  • 4.0.0-canary.34

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to PayloadCMS version 3.90.0 or later, or to canary version 4.0.0-canary.34 or later, where this vulnerability is fixed. No other mitigation is specified or required once the update is applied.

Description

## Impact A malicious SVG file upload could bypass sanitization, be stored, and execute attacker-controlled JavaScript (XSS) after a user downloads it and opens it. **You are affected if:** - You have a collection configured to upload and allow SVG files which can then be downloaded by users. ## Patches The fix validates SVG content on every upload path and hardens SVG/XML delivery so stored SVGs cannot frame attacker content. Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ## Workarounds Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP. These mitigations reduce exposure but do not replace upgrading when the patched release is available.

References

Community reviews

Loading reviews…