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.
Fixed in 0.4.11. The server now checks the Idempotent-Replayed header and rejects replayed PaymentIntents.
There are no workarounds available for this vulnerability.
{
"github_reviewed": true,
"cwe_ids": [
"CWE-697"
],
"nvd_published_at": null,
"github_reviewed_at": "2026-03-29T15:11:30Z",
"severity": "MODERATE"
}