Payment bypass via unbound Stripe PaymentIntent
Published May 5, 2026 · Updated May 5, 2026
Authorization bypass in WPMU DEV Forminator Forms 1.52.0 and earlier allows remote attackers to submit underpaid Stripe forms. The public payment handler trusts an attacker-supplied paymentid as a succeeded Stripe PaymentIntent without binding its amount or ownership to the current form submission. A previously succeeded low-value intent is required, and reuse marks a higher-value form paid without collecting the full amount.
Summary
What happened
Authorization bypass in WPMU DEV Forminator Forms 1.52.0 and earlier allows remote attackers to submit underpaid Stripe forms. The public payment handler trusts an attacker-supplied paymentid as a succeeded Stripe PaymentIntent without binding its amount or ownership to the current form submission. A previously succeeded low-value intent is required, and reuse marks a higher-value form paid without collecting the full amount.
The record
- CVE
- CVE-2026-2729
- Published
- May 5, 2026
- Updated
- May 5, 2026
- Vendor
- AIOSEO Plugin Team
- Product
- Forminator Forms
- Classifications
- CWE-639, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2026CVE publishedPublication date reported by the CVE source.
- May 5, 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.52.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