# CVE-2026-113355: Chatwoot before 4.14.0 Stored XSS via Help Center Video Embed Links


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-v2m9-jwmw-39xc

## What is CVE-2026-113355?

CVE-2026-113355 is a medium-severity vulnerability in chatwoot, published on 20 Oct 2026. 

### Official description

Chatwoot before 4.14.0 contains a stored cross-site scripting vulnerability that allows account administrators to inject JavaScript by crafting video-embed links in Help Center articles. Attackers can use angle-bracket link destinations with double quotes to break out of the unescaped iframe src attribute in render_embed_from_match, executing scripts for public visitors and stealing cw_conversation widget tokens.

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

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


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

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

## Is CVE-2026-113355 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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