Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8mhj-rffc-rcvw | mppx has Stripe charge credential replay via missing idempotency check |
Fri, 03 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:wevm:mppx:*:*:*:*:*:node.js:*:* | |
| Metrics |
cvssV3_1
|
Wed, 01 Apr 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wevm
Wevm mppx |
|
| Vendors & Products |
Wevm
Wevm mppx |
Tue, 31 Mar 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 31 Mar 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | mppx has Stripe charge credential replay via missing idempotency check | |
| Weaknesses | CWE-697 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-31T18:53:01.611Z
Reserved: 2026-03-26T15:57:52.324Z
Link: CVE-2026-34210
Updated: 2026-03-31T18:50:25.187Z
Status : Analyzed
Published: 2026-03-31T15:16:18.207
Modified: 2026-04-03T16:17:49.840
Link: CVE-2026-34210
No data.
OpenCVE Enrichment
Updated: 2026-04-03T21:17:43Z
Github GHSA