# CVE-2025-0470: Forminator <= 1.38.2 - Reflected Cross-Site Scripting via Title Parameter

> Unauthenticated attackers can inject arbitrary web scripts via the title parameter, executing code in victim browsers if they click a crafted link.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-5mrr-3jvw-jc5j

## What is CVE-2025-0470?

CVE-2025-0470 is a medium-severity cross-site scripting vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the title parameter in all versions up to, and including, 1.38.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Wpmudev Forminator Forms.

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

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

## Is CVE-2025-0470 being exploited?

There is no known exploitation of CVE-2025-0470 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-3479](https://insights.sbomify.com/CVE-2025-3479/): Forminator <= 1.42.0 - Order Replay Vulnerability (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0470 is a medium-severity cross-site scripting vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0470 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-0470/ (Markdown: https://insights.sbomify.com/CVE-2025-0470/index.md)
```

## Sources

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

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