# CVE-2023-6842: Formidable Forms <= 6.7 - Authenticated (Administrator+) Stored Cross-Site Scripting

> Administrators can inject scripts via form labels, potentially affecting other users in multi-site or specific configurations.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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:** 9 Jan 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hrg2-9cxg-f9w6

## What is CVE-2023-6842?

CVE-2023-6842 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 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Formidable Forms – Contact Form, Survey, Quiz, Payment, Calculator Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the name field label and description field label parameter in all versions up to 6.7 (inclusive) due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. By default, this only affects multi-site installations and installations where unfiltered_html has been disabled. However, in the formidable settings admins can extend form creation, deletion and other management permissions to other user types, which makes it possible for this vulnerability to be exploited by lower level user types as long as they have been granted the proper permissions.

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

## Which versions are affected by CVE-2023-6842?

It affects 1 product.


Products: Strategy11 Formidable Form Builder.

## How do I fix CVE-2023-6842?

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

## Is CVE-2023-6842 being exploited?

There is no known exploitation of CVE-2023-6842 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-2019-15780](https://insights.sbomify.com/CVE-2019-15780/): Deserialization in n/a (critical 9.8)
- [CVE-2021-24884](https://insights.sbomify.com/CVE-2021-24884/): Formidable Form Builder < 4.09.05 - Unauthenticated Stored Cross-Site Scripting (critical 9.6)
- [CVE-2017-20192](https://insights.sbomify.com/CVE-2017-20192/): Formidable Form Builder < 2.05.03 - Unauthenticated Stored Cross-Site Scripting (high 8.3)
- [CVE-2023-24419](https://insights.sbomify.com/CVE-2023-24419/): WordPress Formidable Forms Plugin <= 5.5.6 is vulnerable to Cross Site Request Forgery (CSRF) (high 7.1)
- [CVE-2023-6830](https://insights.sbomify.com/CVE-2023-6830/): Formidable Forms <= 6.7 - HTML Injection (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6842 and fix it if it is affected.

What it is: CVE-2023-6842 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 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6842 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-2023-6842/ (Markdown: https://insights.sbomify.com/CVE-2023-6842/index.md)
```

## Sources

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

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