Vulnerability in @payloadcms/plugin-ecommerce (CVE-2026-105850)
Summary
Vulnerability in @payloadcms/plugin-ecommerce (CVE-2026-105850). Data can be tampered with by attackers. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
Impact
When using the Stripe payment adapter, an order confirmation could be processed more than once under certain conditions.
You are affected if:
- You use
@payloadcms/plugin-ecommercewith the Stripe payment adapter.
Deployments that do not use the Stripe payment flow are not affected.
Patches
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds
Ensure Stripe order confirmations can only be processed once. This is a temporary mitigation; upgrading to a patched version is recommended.
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-105850 has been found in @payloadcms/plugin-ecommerce.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade @payloadcms/plugin-ecommerce to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "@payloadcms/plugin-ecommerce CVE-2026-105850" on the vendor's site.
CVE-2026-105850 (@payloadcms/plugin-ecommerce) — CWE-837 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.0.0-canary.34 — apply immediately
Workaround: Ensure Stripe order confirmations can only be processed once.
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-837) exists in @payloadcms/plugin-ecommerce.
Check the vendor advisory for the affected versions of @payloadcms/plugin-ecommerce.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 4.0.0-canary.34.
Workaround: Ensure Stripe order confirmations can only be processed once.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@payloadcms/plugin-ecommerce' . 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-ecommerce' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/plugin-ecommerceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Ensure Stripe order confirmations can only be processed once.パッチが適用されるまでの応急処置として、Ensure Stripe order confirmations can only be processed once. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @payloadcms/plugin-ecommerce to 4.0.0-canary.34ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com