# CVE-2026-11881: Fluent Forms < 6.2.6 - Contributor+ Stored XSS via Date/Time Field

> Contributors can inject malicious scripts into form fields, leading to stored XSS that executes in visitors' browsers, including administrators.

- **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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-x2rq-2q3v-fw75

## What is CVE-2026-11881?

CVE-2026-11881 is a medium-severity cross-site scripting vulnerability in Unknown Fluent Forms, published on 30 Jul 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 Fluent Forms  WordPress plugin before 6.2.6 does not sanitise and escape one of its form field configuration settings before outputting it inside an inline script when a form is rendered, which could allow users with a role as low as Contributor (with delegated form-management permission, and therefore lacking the unfiltered_html capability, e.g. in a multisite setup) to perform Stored Cross-Site Scripting attacks that execute in the browser of any visitor who loads the form, including administrators previewing it.

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

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


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

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

## Is CVE-2026-11881 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11881 is a medium-severity cross-site scripting vulnerability in Unknown Fluent Forms, published on 30 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11881 exists.

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

## Sources

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

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