# CVE-2024-1415: Responsive Contact Form Builder & Lead Generation Plugin <= 1.8.9 - Cross-Site Request Forgery


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mg34-mgcp-24mq

## What is CVE-2024-1415?

CVE-2024-1415 is a medium-severity vulnerability in themehunk Lead Form Builder & Contact Form, published on 2 May 2024. 

### Official description

The Responsive Contact Form Builder & Lead Generation Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.8.9. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to invoke those functions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. These actions may result in form deletion, and lead signup as well as file upload.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2024-1415 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1415 is a medium-severity vulnerability in themehunk Lead Form Builder & Contact Form, published on 2 May 2024. 
Exploitation: There is no known exploitation of CVE-2024-1415 in the wild and no public exploit code.

Affected product: themehunk Lead Form Builder & Contact Form. 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-1415/ (Markdown: https://insights.sbomify.com/CVE-2024-1415/index.md)
```

## Sources

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

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