CVE-2026-2729

Forminator – Contact Form, Payment Form & Custom Form Builder <= 1.52.0 - Missing Authorization to Unauthenticated Stripe PaymentIntent Reuse / Underpayment Bypass via 'paymentid' Parameter

2026-05-04 17:34
Kittipat Jitphonchana

Strategic Overview

Status
Patched in 1.52.1
Affected Plugin
Forminator Forms – Contact Form, Payment Form & Custom Form Builder
Affected Version
<= 1.52.0
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-2729
View all Forminator Forms – Contact Form, Payment Form & Custom Form Builder vulnerabilities

At a glance

CVE-2026-2729 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Forminator Forms WordPress plugin, affecting versions <= 1.52.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.52.1; sites on affected versions should update now. Disclosed May 2026, reported by Kittipat Jitphonchana.

Vulnerability Overview

The Forminator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.52.0. This is due to the plugin not properly verifying that a user is authorized to perform an action when processing attacker-supplied Stripe PaymentIntent identifiers in the public payment flow. This makes it possible for unauthenticated attackers to submit high-value paid forms as completed by reusing a previously succeeded low-value Stripe PaymentIntent, resulting in underpayment/payment bypass conditions.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Forminator Forms <= 1.52.0 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Forminator Forms the fix is 1.52.1: builds <= 1.52.0 are affected, anything from 1.52.1 onward is not.

Remediation

Update to version 1.52.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Forminator Forms 1.52.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2729https://www.wordfence.com/threat-intel/vulnerabilities/id/1afb94ab-b3ba-4598-8ff4-f9ffc6717371https://nvd.nist.gov/vuln/detail/CVE-2026-2729

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C