# CVE-2026-116139: WWBN AVideo 26.0 through 29.3.0 Stored XSS via Comment Markdown Rendering


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-cx46-26xc-2w7f, GHSA-r52j-79hv-6mmf

## What is CVE-2026-116139?

CVE-2026-116139 is a medium-severity vulnerability in WWBN AVideo, published on 25 Oct 2026. 

### Official description

WWBN AVideo 26.0 through 29.3.0 contains a stored cross-site scripting vulnerability that allows authenticated commenters to inject JavaScript because markDownToHTML() preserves event-handler attributes in leading HTML blocks. Attackers can post a comment starting with an img tag carrying an onerror handler, which bypasses the inline sanitizer and executes in viewers' browsers under the application origin.

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

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


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

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

## Is CVE-2026-116139 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116139 is a medium-severity vulnerability in WWBN AVideo, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116139 in the wild and no public exploit code.

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

## Sources

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

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