# CVE-2025-6463: Path traversal in Forminator Forms – Contact Form, Payment Form & Custom Form Builder

> Unauthenticated attackers can delete arbitrary files via form submissions, potentially leading to remote code execution by deleting critical configuration files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 2 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-w787-9chh-w9q4

## What is CVE-2025-6463?

CVE-2025-6463 is a high-severity path traversal vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 2 Jul 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 arbitrary file deletion due to insufficient file path validation in the 'entry_delete_upload_files' function in all versions up to, and including, 1.44.2. This makes it possible for unauthenticated attackers to include arbitrary file paths in a form submission. The file will be deleted when the form submission is deleted, whether by an Administrator or via auto-deletion determined by plugin settings. This can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Incsub Forminator.

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

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

## Is CVE-2025-6463 being exploited?

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

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

- [CVE-2023-4596](https://insights.sbomify.com/CVE-2023-4596/): Forminator <= 1.24.6 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2025-6464](https://insights.sbomify.com/CVE-2025-6464/): Deserialization in Forminator Forms – Contact Form, Payment Form & Custom Form Builder (high 7.5)
- [CVE-2024-7389](https://insights.sbomify.com/CVE-2024-7389/): Forminator <= 1.29.1 - HubSpot Developer API Key Sensitive Information Exposure (high 7.5)
- [CVE-2024-31077](https://insights.sbomify.com/CVE-2024-31077/): SQL injection in Forminator (high 7.2)
- [CVE-2024-1794](https://insights.sbomify.com/CVE-2024-1794/): Forminator <= 1.29.0 - Unauthenticated Stored Cross-Site Scripting via File Upload (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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