GHSA-r9v2-gg2j-22q5
Payload: Insufficient Access Control in Stripe REST Proxy
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | @payloadcms/plugin-stripe | < 3.90.0 | 3.90.0 |
| npm | @payloadcms/plugin-stripe | >= 4.0.0-canary.0, < 4.0.0-canary.34 | 4.0.0-canary.34 |
Details
As written in the advisory (Markdown source, shown as plain text).
## Impact
An authenticated user could perform unintended Stripe operations through the optional Stripe REST proxy.
**You are affected if ALL of these are true:**
- Your application uses `@payloadcms/plugin-stripe`.
- The optional Stripe REST proxy is enabled.
- An authenticated user can reach the proxy.
Deployments that do not enable the Stripe REST proxy are not affected.
## Patches
Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.
## Workarounds
Upgrading to a patched version is recommended.
If you cannot upgrade immediately, disable the Stripe REST proxy. If it must remain enabled, restrict access to trusted users and only the required Stripe operations.
References
External links from the advisory. They lead to third-party sites.