# CVE-2026-105848: Payload plugin-stripe insufficient access control in REST proxy

Source: https://junglewise.ai/threats/cve-2026-105848-payload-insufficient-access-control-in-stripe-rest-proxy  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-06. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-105848 · Severity: medium · CVSS 4 · Published 2026-10-06

Payload CMS is a headless content management system with optional Stripe payment integration. The Stripe REST proxy feature has insufficient access controls, allowing any authenticated user to perform unintended payment operations, potentially leading to unauthorized transactions or data exposure. This affects applications that enable the optional Stripe proxy and allow any authenticated user access to it.

Vendors: [npm](https://junglewise.ai/threats/vendors/npm), [Payload CMS](https://junglewise.ai/threats/vendors/payload-cms).

## Quick answers

**Is CVE-2026-105848 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-105848 being exploited in the wild.

**How severe is CVE-2026-105848?** Medium severity, with a CVSS score of 4, published 6 October 2026.

**Which products and versions are affected?** @payloadcms/plugin-stripe (npm) SEMVER:introduced=0,fixed=3.90.0; Payload CMS Plugin-Stripe < 3.90.0, >= 4.0.0-canary.0 and < 4.0.0-canary.34.

**Is there a fix for CVE-2026-105848?** Yes. @payloadcms/plugin-stripe (npm): upgrade to 3.90.0 or later. Until then: Disable the Stripe REST proxy if not required. If the proxy must remain enabled, restrict access to only trusted users and implement fine-grained access controls to allow only the required Stripe operations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-105848 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-105848?** Check whether you run @payloadcms/plugin-stripe (npm) or Payload CMS Plugin-Stripe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @payloadcms/plugin-stripe (npm): upgrade to 3.90.0 or later

  ```sh
  npm install @payloadcms/plugin-stripe@3.90.0
  ```


Disable the Stripe REST proxy if not required. If the proxy must remain enabled, restrict access to only trusted users and implement fine-grained access controls to allow only the required Stripe operations.

## Technical details

The Stripe REST proxy in @payloadcms/plugin-stripe lacks proper authorization checks, allowing authenticated users to invoke arbitrary Stripe API operations beyond their intended scope. An attacker with low-privilege authentication can reach the proxy over the network and perform unintended actions on Stripe accounts. The vulnerability requires the proxy to be explicitly enabled and reachable by authenticated users.

## Affected products

- Payload CMS plugin-stripe < 3.90.0, >= 4.0.0-canary.0 and < 4.0.0-canary.34

## Identifiers

- CVE-2026-105848
- GHSA-r9v2-gg2j-22q5

## Timeline

- 2026-09-18: disclosed
- 2026-10-06: advisory
- 2026-09-18: patched

## References

- [https://github.com/payloadcms/payload/security/advisories/GHSA-r9v2-gg2j-22q5](https://github.com/payloadcms/payload/security/advisories/GHSA-r9v2-gg2j-22q5)