# CVE-2024-2772: Cross-site scripting in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

> Authenticated attackers can inject malicious scripts into Fluent Forms settings, leading to script execution on victim pages.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-736r-j9wv-3f4j

## What is CVE-2024-2772?

CVE-2024-2772 is a medium-severity cross-site scripting vulnerability in techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder, published on 18 May 2024. Any signed-in user can exploit it over the network, 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 Stored Cross-Site Scripting via form settings in all versions up to, and including, 5.1.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with access to the Fluent Forms settings, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This can be chained with CVE-2024-2771 for a low-privileged user to inject malicious web scripts.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Fluentforms Contact Form.

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

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

## Is CVE-2024-2772 being exploited?

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

## 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-2782](https://insights.sbomify.com/CVE-2024-2782/): Missing authorization in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2772 is a medium-severity cross-site scripting vulnerability in techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder, published on 18 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2772 in the wild and no public exploit code.

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-2772/ (Markdown: https://insights.sbomify.com/CVE-2024-2772/index.md)
```

## Sources

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

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