# CVE-2026-2729: Missing authorization in Forminator Forms – Contact Form, Payment Form & Custom Form Builder

> Unauthenticated attackers can bypass payment verification by reusing low-value Stripe PaymentIntents to submit high-value forms, leading to underpayment.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-xf3j-2pwf-m9rm

## What is CVE-2026-2729?

CVE-2026-2729 is a medium-severity missing authorization vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-2729?


## How do I fix CVE-2026-2729?

No fix has been published for CVE-2026-2729 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2729 being exploited?

There is no known exploitation of CVE-2026-2729 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2729 and fix it if it is affected.

What it is: CVE-2026-2729 is a medium-severity missing authorization vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2729 in the wild and no public exploit code.

Affected product: wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2729/ (Markdown: https://insights.sbomify.com/CVE-2026-2729/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2729
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2729
- OSV: https://osv.dev/vulnerability/CVE-2026-2729

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2729/
Summaries are generated and may contain mistakes; the official description above is the record.