# CVE-2024-7782: Path traversal in Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder

> Administrators can delete arbitrary files via path traversal, potentially leading to remote code execution.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-7x38-847r-875x

## What is CVE-2024-7782?

CVE-2024-7782 is a high-severity path traversal vulnerability in bitpressadmin Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder, published on 20 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the iconRemove function in versions 2.0 to 2.13.4. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-7782?

It affects 1 product.


Products: Bitapps Contact Form Builder.

## How do I fix CVE-2024-7782?

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

## Is CVE-2024-7782 being exploited?

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

## Other vulnerabilities in bitpressadmin Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder

- [CVE-2024-7777](https://insights.sbomify.com/CVE-2024-7777/): Path traversal in Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (critical 9.0)
- [CVE-2024-7702](https://insights.sbomify.com/CVE-2024-7702/): SQL injection in Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (high 7.2)
- [CVE-2024-7780](https://insights.sbomify.com/CVE-2024-7780/): SQL injection in Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (high 7.2)
- [CVE-2024-7775](https://insights.sbomify.com/CVE-2024-7775/): File upload in Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (medium 5.5)
- [CVE-2024-1640](https://insights.sbomify.com/CVE-2024-1640/): Missing authorization in Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7782 and fix it if it is affected.

What it is: CVE-2024-7782 is a high-severity path traversal vulnerability in bitpressadmin Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder, published on 20 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7782 in the wild and no public exploit code.

Affected product: bitpressadmin Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact 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-2024-7782/ (Markdown: https://insights.sbomify.com/CVE-2024-7782/index.md)
```

## Sources

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

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