Order replay via reused Stripe PaymentIntent
Published Apr 16, 2025 · Updated Jul 25, 2026
Order replay in Contact Form 7 6.0.5 and earlier allows remote attackers to trigger repeated success emails with one Stripe PaymentIntent. The wpcf7_stripe_skip_spam_check function accepts a user-controlled PaymentIntent identifier without checking whether the intent was already consumed, so later submissions reuse it. Stripe integration must be active and the intent must have succeeded; Stripe charges only once, but administrators can fulfill multiple emailed orders.
Summary
What happened
Order replay in Contact Form 7 6.0.5 and earlier allows remote attackers to trigger repeated success emails with one Stripe PaymentIntent. The wpcf7_stripe_skip_spam_check function accepts a user-controlled PaymentIntent identifier without checking whether the intent was already consumed, so later submissions reuse it. Stripe integration must be active and the intent must have succeeded; Stripe charges only once, but administrators can fulfill multiple emailed orders.
The record
- CVE
- CVE-2025-3247
- Published
- Apr 16, 2025
- Updated
- Jul 25, 2026
- Vendor
- Rock Lobster Inc.
- Product
- Contact Form 7
- Classifications
- CWE-354, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Jul 25, 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 <=6.0.5
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