# CVE-2026-116202: YesWiki before 4.7.0 Stored XSS via ImageField SVG Upload


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-c5q6-7233-3v6g, GHSA-vp3x-8xh2-ppc9

## What is CVE-2026-116202?

CVE-2026-116202 is a medium-severity vulnerability in yeswiki, published on 25 Oct 2026. 

### Official description

YesWiki before 4.7.0 contains a stored cross-site scripting vulnerability that allows low-privilege authenticated users to upload unsanitized SVG files through the bazar ImageField class. Attackers can submit a malicious SVG via the image field of the entries API, which is served as image/svg+xml and executes script for users viewing the entry or file.

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

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


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

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

## Is CVE-2026-116202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116202 is a medium-severity vulnerability in yeswiki, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116202 exists.

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

## Sources

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

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