# CVE-2024-1640: Missing authorization in Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder

> Unauthenticated attackers can modify form submissions due to insufficient validation in the Bit Form WordPress plugin.

- **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:** 13 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hj83-c8q3-6fc2

## What is CVE-2024-1640?

CVE-2024-1640 is a medium-severity missing authorization vulnerability in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Contact Form Builder Plugin: Multi Step Contact Form, Payment Form, Custom Contact Form Plugin by Bit Form plugin for WordPress is vulnerable to unauthorized modification of data due to a insufficient user validation on the bitforms_update_form_entry AJAX action in all versions up to, and including, 2.10.1. This makes it possible for unauthenticated attackers to modify form submissions.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Bitapps Contact Form Builder.

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

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

## Is CVE-2024-1640 being exploited?

There is no known exploitation of CVE-2024-1640 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-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-7782](https://insights.sbomify.com/CVE-2024-7782/): Path traversal in Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (high 8.7)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1640 is a medium-severity missing authorization vulnerability in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder, published on 13 Mar 2024. 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-1640 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-1640/ (Markdown: https://insights.sbomify.com/CVE-2024-1640/index.md)
```

## Sources

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

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