# CVE-2026-85641: Formidable Forms 6.34 - Unauthenticated Stored Content Injection via 'updated_by' Parameter

> Unauthenticated attackers can inject malicious HTML into form entries via the updated_by parameter, leading to stored XSS in the admin view.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-c92r-vvxr-8r78

## What is CVE-2026-85641?

CVE-2026-85641 is a medium-severity cross-site scripting vulnerability in Unknown Formidable Forms, published on 16 Sep 2026. 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  WordPress plugin before 6.35 does not restrict who can set the identifier recording which user last edited a form entry, and relies on that identifier when deciding whether to strip HTML from stored entry values, allowing unauthenticated visitors to have markup rendered in the admin entry view that would otherwise be removed, and to attribute their submission to an administrator who never made it.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-85641?


## How do I fix CVE-2026-85641?

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

## Is CVE-2026-85641 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85641 and fix it if it is affected.

What it is: CVE-2026-85641 is a medium-severity cross-site scripting vulnerability in Unknown Formidable Forms, published on 16 Sep 2026. 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-2026-85641 in the wild and no public exploit code.

Affected product: Unknown Formidable Forms. 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-2026-85641/ (Markdown: https://insights.sbomify.com/CVE-2026-85641/index.md)
```

## Sources

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

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