# CVE-2024-13451: Contact Form by Bit Form <= 2.17.5 - Unauthenticated Sensitive Information Exposure

> Unauthenticated attackers can extract sensitive uploaded files due to insufficient directory listing prevention and lack of file name randomization in the Bit Form plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 2 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9p36-p37c-r4fp

## What is CVE-2024-13451?

CVE-2024-13451 is a medium-severity vulnerability in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder, published on 2 Jul 2025. An attacker can exploit it over the internet without logging in, 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 Sensitive Information Exposure in all versions up to, and including, 2.17.4 via file uploads due to insufficient directory listing prevention and lack of randomization of file names. This makes it possible for unauthenticated attackers to extract sensitive data including files uploaded via a form. The vulnerability was partially patched in version 2.17.5.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Bitapps Bit Form.

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

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

## Is CVE-2024-13451 being exploited?

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

## Other vulnerabilities in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder

- [CVE-2024-43249](https://insights.sbomify.com/CVE-2024-43249/): WordPress Bit Form Pro plugin <= 2.6.4 - Authenticated Arbitrary File Upload vulnerability (critical 9.9)
- [CVE-2022-4774](https://insights.sbomify.com/CVE-2022-4774/): Bit Form < 1.9 - RCE via Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2024-43248](https://insights.sbomify.com/CVE-2024-43248/): WordPress Bit Form Pro plugin <= 2.6.4 - Unauthenticated Arbitrary File Deletion vulnerability (high 8.6)
- [CVE-2024-43250](https://insights.sbomify.com/CVE-2024-43250/): WordPress Bit Form Pro plugin <= 2.6.4 - Authenticated Plugin Settings Change vulnerability (high 7.1)
- [CVE-2024-43251](https://insights.sbomify.com/CVE-2024-43251/): WordPress Bit Form Pro plugin <= 2.6.4 - Authenticated Sensitive Data Exposure vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13451 is a medium-severity vulnerability in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder, published on 2 Jul 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-2024-13451 in the wild and no public exploit code.

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

## Sources

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

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