# CVE-2025-3479: Forminator <= 1.42.0 - Order Replay Vulnerability

> Unauthenticated attackers can replay Stripe payment intents to trick administrators into fulfilling multiple orders for a single payment.

- **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:** 17 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-5xv8-fpcw-hxq7

## What is CVE-2025-3479?

CVE-2025-3479 is a medium-severity vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Order Replay in all versions up to, and including, 1.42.0 via the 'handle_stripe_single' function due to insufficient validation on a user controlled key. This makes it possible for unauthenticated attackers to reuse a single Stripe PaymentIntent for multiple transactions. Only the first transaction is processed via Stripe, but the plugin sends a successful email message for each transaction, which may trick an administrator into fulfilling each order.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2025-3479?

It affects 1 product.


Products: Wpmudev Forminator Forms.

## How do I fix CVE-2025-3479?

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

## Is CVE-2025-3479 being exploited?

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

## Other vulnerabilities in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder

- [CVE-2024-10402](https://insights.sbomify.com/CVE-2024-10402/): Missing authorization in Forminator Forms – Contact Form, Payment Form & Custom Form Builder (high 7.5)
- [CVE-2025-5341](https://insights.sbomify.com/CVE-2025-5341/): Cross-site scripting in Forminator Forms – Contact Form, Payment Form & Custom Form Builder (medium 6.4)
- [CVE-2025-3487](https://insights.sbomify.com/CVE-2025-3487/): Forminator <= 1.42.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'limit' (medium 6.4)
- [CVE-2025-0469](https://insights.sbomify.com/CVE-2025-0469/): Forminator <= 1.39.2 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2025-0470](https://insights.sbomify.com/CVE-2025-0470/): Forminator <= 1.38.2 - Reflected Cross-Site Scripting via Title Parameter (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3479 and fix it if it is affected.

What it is: CVE-2025-3479 is a medium-severity vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 17 Apr 2025. 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-2025-3479 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-2025-3479/ (Markdown: https://insights.sbomify.com/CVE-2025-3479/index.md)
```

## Sources

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

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