# CVE-2026-106469: Gutenverse Form < 3.0.11 - Contributor+ Stored XSS via SVG Icon

> Authenticated contributors can inject malicious SVG code into forms, leading to stored XSS and potential admin session hijacking.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-77vr-jjv3-x5q5

## What is CVE-2026-106469?

CVE-2026-106469 is a medium-severity cross-site scripting vulnerability in Unknown Gutenverse Form, published on 14 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Gutenverse Form  WordPress plugin before 3.0.11 does not sanitize SVG icon markup stored in its form blocks before it is decoded and inserted into the page in the browser, allowing authenticated users with Contributor-level access and above to store malicious SVG that executes JavaScript in the session of any user who views or previews the affected form, such as an administrator reviewing a pending post.

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

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


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

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

## Is CVE-2026-106469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106469 is a medium-severity cross-site scripting vulnerability in Unknown Gutenverse Form, published on 14 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-106469 in the wild and no public exploit code.

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

## Sources

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

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