# CVE-2024-13450: Contact Form by Bit Form <= 2.17.4 - Authenticated (Administrator+) Server-Side Request Forgery

> Administrators can exploit a Server-Side Request Forgery vulnerability in the Webhooks integration to access internal services.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-ppjh-j3rw-5x4r

## What is CVE-2024-13450?

CVE-2024-13450 is a low-severity server-side request forgery vulnerability in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder, published on 25 Jan 2025. 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 Server-Side Request Forgery in all versions up to, and including, 2.17.4 via the Webhooks integration. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The vulnerability can also be exploited in Multisite environments.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Bitapps Contact Form Builder.

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

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

## Is CVE-2024-13450 being exploited?

There is no known exploitation of CVE-2024-13450 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-13450 and fix it if it is affected.

What it is: CVE-2024-13450 is a low-severity server-side request forgery vulnerability in bitpressadmin Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder, published on 25 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13450 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-13450/ (Markdown: https://insights.sbomify.com/CVE-2024-13450/index.md)
```

## Sources

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

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