Vulnerability in @payloadcms/plugin-stripe (CVE-2026-105848)
Summary
Vulnerability in @payloadcms/plugin-stripe (CVE-2026-105848). Confidential information can be exposed externally. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105848 has been found in @payloadcms/plugin-stripe.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade @payloadcms/plugin-stripe to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "@payloadcms/plugin-stripe CVE-2026-105848" on the vendor's site.
CVE-2026-105848 (@payloadcms/plugin-stripe) — CWE-749 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.0.0-canary.34 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-749) exists in @payloadcms/plugin-stripe.
Check the vendor advisory for the affected versions of @payloadcms/plugin-stripe.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 4.0.0-canary.34.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@payloadcms/plugin-stripe' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@payloadcms/plugin-stripe' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/plugin-stripeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @payloadcms/plugin-stripe to 4.0.0-canary.34ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com