mppx has Stripe charge credential replay via missing idempotency check

高 8.1CVE-2026-34210 · GHSA-8mhj-rffc-rcvw · 31/03/2026 公開 · 24/07/2026 更新

要点

CVE-2026-34210 は mppx (wevm), mppx に影響する深刻度「高」 (CVSS 8.1) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.51%（全脆弱性の 43.7% より高い）。
対処：0.4.11 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
mppx wevm	`< 0.4.11`	`0.4.11`
mppx npm	`< 0.4.11`	`0.4.11`

概要

Impact

The stripe/charge payment method did not check Stripe's Idempotent-Replayed response header when creating PaymentIntents. An attacker could replay a valid credential containing the same spt token against a new challenge, and the server would accept the replayed Stripe PaymentIntent as a new successful payment without actually charging the customer again. This allowed an attacker to pay once and consume unlimited resources by replaying the credential.

Patches

Fixed in 0.4.11. The server now checks the Idempotent-Replayed header and rejects replayed PaymentIntents.

Workarounds

There are no workarounds available for this vulnerability.

NVD の説明

mppx is a TypeScript interface for machine payments protocol. Prior to version 0.4.11, the stripe/charge payment method did not check Stripe's Idempotent-Replayed response header when creating PaymentIntents. An attacker could replay a valid credential containing the same spt token against a new challenge, and the server would accept the replayed Stripe PaymentIntent as a new successful payment without actually charging the customer again. This allowed an attacker to pay once and consume unlimited resources by replaying the credential. This issue has been patched in version 0.4.11.