CVE Intelligence
Critical

CVE-2026-105848 — Payload: Insufficient Access Control in Stripe REST Proxy

Payload is a free and open source headless content management system. In @payloadcms/plugin-stripe versions before 3.90.0 and canary versions before 4.0.0-canary.34, an authenticated user who can reach the enabled optional Stripe REST proxy can perform unintended Stripe operations. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

Published Oct 6, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.24%
ahead of 15% of scored CVEs · Oct 15, 2026
Affects
@payloadcms
Payload and 2 more
CVSS base
9.6
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Npm @payloadcms/plugin-stripe: fixed in version 3.90.0 — github.com (GitHub Security Advisories)
  • Npm @payloadcms/plugin-stripe: fixed in version 4.0.0-canary.34 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (@payloadcms Payload, @payloadcms Plugin-stripe, Npm @payloadcms/plugin-stripe).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
@payloadcms Payload version 4.0.0-canary31version 4.0.0-canary23version 4.0.0-canary24version 4.0.0-canary25version 4.0.0-canary26version 4.0.0-canary27version 4.0.0-canary28version 4.0.0-canary29
and 27 more version 4.0.0-canary3version 4.0.0-canary30version 4.0.0-canary32version 4.0.0-canary33version 4.0.0-canary4version 4.0.0-canary5version 4.0.0-canary6version 4.0.0-canary7version 4.0.0-canary8version 4.0.0-canary9version 4.0.0-canary21< 3.90.0version 4.0.0-canary0version 4.0.0-canary1version 4.0.0-canary10version 4.0.0-canary11version 4.0.0-canary12version 4.0.0-canary13version 4.0.0-canary14version 4.0.0-canary15version 4.0.0-canary16version 4.0.0-canary17version 4.0.0-canary18version 4.0.0-canary19version 4.0.0-canary2version 4.0.0-canary20version 4.0.0-canary22
Vulnerable NIST National Vulnerability Database
@payloadcms Payload version >= 4.0.0-canary.0, < 4.0.0-canary.34version < 3.90.0 Vulnerable CVE Program (cve.org) e CISA ADP
@payloadcms Plugin-stripe version < 3.90.0version >= 4.0.0-canary.0, < 4.0.0-canary.34 Vulnerable CVE Program (cve.org) e CISA ADP
Npm @payloadcms/plugin-stripe < 3.90.0≥ 4.0.0-canary.0 and < 4.0.0-canary.34 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.4 CVSS 4.0 Medium — — security-advisories@github.com via NIST National Vulnerability Database
6.4 CVSS 4.0 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
9.6 CVSS 3.1 Critical 3.1 5.8 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-749

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.25%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · npm/@payloadcms/plugin-stripe
    Oct 14, 2026 · GitHub Security Advisories
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · payloadcms/payload
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 6.4 → 9.6
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · Undergoing Analysis → Analyzed
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · payloadcms/payload, @payloadcms/plugin-stripe
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.4
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Undergoing Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 6, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

@payloadcms
every CVE for this vendor
CWE-749
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-106100 Payload: Field-level write access bypass in Payload on MongoDB 9d
  • CVE-2026-105867 Payload: Client uploads could overwrite S3 objects 9d
  • CVE-2026-105868 Payload: Uploaded XML files could execute same-origin JavaScript 9d
  • CVE-2026-105865 Payload: Incomplete validation during the upload file lifecycle 9d
  • CVE-2026-105864 Payload: Cross-tenant create in @payloadcms/plugin-multi-tenant 9d
  • CVE-2026-105866 Payload: Unauthenticated account-lockout denial of service 9d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-105848 is "Payload: Insufficient Access Control in Stripe REST Proxy", rated Critical. It affects Payload (@payloadcms); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.6 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.