# CVE-2026-9278: Form Builder CP < 1.2.47 - Editor+ Stored XSS via form_structure

> Authenticated editors can inject malicious scripts into form configurations, leading to stored XSS attacks against site visitors.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-x9r5-r92q-89hf

## What is CVE-2026-9278?

CVE-2026-9278 is a medium-severity cross-site scripting vulnerability in Unknown Form Builder CP, published on 15 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Form Builder CP WordPress plugin before 1.2.47 does not properly sanitize a form configuration value before storing it and using it as part of a client-side script execution, allowing authenticated users with Editor-level access and above to perform Stored Cross-Site Scripting attacks against any visitor of a page rendering the affected form, even when the `unfiltered_html` capability is disallowed (e.g. in a multisite network).

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


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

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

## Is CVE-2026-9278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9278 is a medium-severity cross-site scripting vulnerability in Unknown Form Builder CP, published on 15 Jun 2026. Any signed-in user can exploit it over the network, 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-9278 exists.

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

## Sources

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

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