# CVE-2024-11188: Cross-site scripting in Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder

> Unauthenticated attackers can inject arbitrary scripts via Custom HTML Form parameters, executing code in victim browsers if they click a crafted link.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xxwr-xc7w-gxgv

## What is CVE-2024-11188?

CVE-2024-11188 is a medium-severity cross-site scripting vulnerability in strategy11team Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder, published on 23 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder plugin for WordPress is vulnerable to POST-Based Reflected Cross-Site Scripting via the Custom HTML Form parameters in all versions up to, and including, 6.16.1.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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

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

It affects 1 product.


Products: Strategy11 Formidable Forms.

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

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

## Is CVE-2024-11188 being exploited?

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

## Other vulnerabilities in strategy11team Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder

- [CVE-2023-2877](https://insights.sbomify.com/CVE-2023-2877/): Formidable Forms < 6.3.1 - Subscriber+ Remote Code Execution (high 8.8)
- [CVE-2023-1405](https://insights.sbomify.com/CVE-2023-1405/): Formidable Forms < 6.2 - Unauthenticated PHP Object Injection (high 7.5)
- [CVE-2024-0660](https://insights.sbomify.com/CVE-2024-0660/): Formidable Forms <= 6.7.2 - Cross-Site Request Forgery to Stored Cross-Site Scripting (medium 6.1)
- [CVE-2024-23522](https://insights.sbomify.com/CVE-2024-23522/): WordPress Formidable Forms plugin <= 6.7 - Content Injection vulnerability (medium 5.3)
- [CVE-2024-6725](https://insights.sbomify.com/CVE-2024-6725/): Formidable Forms <= 6.11.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11188 is a medium-severity cross-site scripting vulnerability in strategy11team Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder, published on 23 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-11188 in the wild and no public exploit code.

Affected product: strategy11team Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom 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-11188/ (Markdown: https://insights.sbomify.com/CVE-2024-11188/index.md)
```

## Sources

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

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