# CVE-2025-15669: Bit Form < 3.1.4 - Admin+ Stored XSS via Conversational Form Progress Label

> High-privilege users can inject JavaScript into Bit Form settings, leading to stored XSS execution in visitors' browsers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-wv7j-rf68-5jcq

## What is CVE-2025-15669?

CVE-2025-15669 is a medium-severity cross-site scripting vulnerability in Unknown Bit Form, published on 1 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Bit Form  WordPress plugin before 3.1.4 does not sanitise one of its conversational-form display settings before rendering it on the public-facing form, allowing high-privilege users (such as administrators, who do not hold the unfiltered_html capability on multisite) to store JavaScript that executes in the browser of any visitor who views the form.

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

## Which versions are affected by CVE-2025-15669?


## How do I fix CVE-2025-15669?

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

## Is CVE-2025-15669 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15669 and fix it if it is affected.

What it is: CVE-2025-15669 is a medium-severity cross-site scripting vulnerability in Unknown Bit Form, published on 1 Aug 2026. An attacker needs administrator access to exploit it, 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-2025-15669 exists.

Affected product: Unknown Bit Form. 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-2025-15669/ (Markdown: https://insights.sbomify.com/CVE-2025-15669/index.md)
```

## Sources

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

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