GHSA-8MHJ-RFFC-RCVW

Vulnerability from github – Published: 2026-03-29 15:11 – Updated: 2026-03-31 18:51
VLAI?
Summary
mppx has Stripe charge credential replay via missing idempotency check
Details

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.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "mppx"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.4.11"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-34210"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-697"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-29T15:11:30Z",
    "nvd_published_at": "2026-03-31T15:16:18Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nThe `stripe/charge` payment method did not check Stripe\u0027s `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.\n\n### Patches\n\nFixed in 0.4.11. The server now checks the `Idempotent-Replayed` header and rejects replayed PaymentIntents.\n\n### Workarounds\n\nThere are no workarounds available for this vulnerability.",
  "id": "GHSA-8mhj-rffc-rcvw",
  "modified": "2026-03-31T18:51:18Z",
  "published": "2026-03-29T15:11:30Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/wevm/mppx/security/advisories/GHSA-8mhj-rffc-rcvw"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34210"
    },
    {
      "type": "WEB",
      "url": "https://github.com/wevm/mppx/commit/b2b1a0b60506fc71aa80b8a025084949dca1a994"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/wevm/mppx"
    },
    {
      "type": "WEB",
      "url": "https://github.com/wevm/mppx/releases/tag/mppx%400.4.11"
    },
    {
      "type": "WEB",
      "url": "https://github.com/wevm/mppx/releases/tag/mppx@0.4.11"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "mppx has Stripe charge credential replay via missing idempotency check"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…