# CVE-2024-2782: Missing authorization in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

> Unauthenticated attackers can modify plugin settings due to missing capability checks on a REST API endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 18 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-5vhv-m5ch-wx48

## What is CVE-2024-2782?

CVE-2024-2782 is a high-severity missing authorization vulnerability in techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder, published on 18 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the /wp-json/fluentform/v1/global-settings REST API endpoint in all versions up to, and including, 5.1.16. This makes it possible for unauthenticated attackers to modify all of the plugin's settings.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Fluentforms Contact Form.

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

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

## Is CVE-2024-2782 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2782 exists.

Public exploit code:

- CVE-2024-2782 Proof-of-Concept  (github_poc): https://github.com/whale93/CVE-2024-2782-PoC
- WordPress FluentForms <= 5.1.16 - Broken Access Control (nuclei): http/cves/2024/CVE-2024-2782.yaml

## Other vulnerabilities in techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

- [CVE-2024-2771](https://insights.sbomify.com/CVE-2024-2771/): Missing authorization in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder (critical 9.8)
- [CVE-2022-3463](https://insights.sbomify.com/CVE-2022-3463/): FluentForm < 4.3.13 - CSV Injection (critical 9.8)
- [CVE-2021-34620](https://insights.sbomify.com/CVE-2021-34620/): CSRF in WP Fluent Forms < 3.6.67 allows stored XSS and Privilege Escalation (high 8.8)
- [CVE-2024-4157](https://insights.sbomify.com/CVE-2024-4157/): Deserialization in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder (high 7.5)
- [CVE-2024-10646](https://insights.sbomify.com/CVE-2024-10646/): Cross-site scripting in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2782 is a high-severity missing authorization vulnerability in techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder, published on 18 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2782 exists.

Affected product: techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational 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-2782/ (Markdown: https://insights.sbomify.com/CVE-2024-2782/index.md)
```

## Sources

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

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