Duplicate fulfillment via replayed Stripe PaymentIntent
Published Apr 17, 2025 · Updated Apr 8, 2026
Order replay in WPMU DEV Forminator 1.42.0 and earlier allows remote attackers to trigger false order-success notifications. The handle_stripe_single function insufficiently validates a user-controlled Stripe PaymentIntent key and treats a replayed intent as a successful transaction. Exploitation requires a Stripe-enabled form and a valid previously paid intent; Stripe processes only the first charge, while repeated success emails can cause duplicate fulfillment.
Summary
What happened
Order replay in WPMU DEV Forminator 1.42.0 and earlier allows remote attackers to trigger false order-success notifications. The handle_stripe_single function insufficiently validates a user-controlled Stripe PaymentIntent key and treats a replayed intent as a successful transaction. Exploitation requires a Stripe-enabled form and a valid previously paid intent; Stripe processes only the first charge, while repeated success emails can cause duplicate fulfillment.
The record
- CVE
- CVE-2025-3479
- Published
- Apr 17, 2025
- Updated
- Apr 8, 2026
- Vendor
- WPMU DEV
- Product
- Forminator
- Classifications
- CWE-354, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.42.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo