# CVE-2026-100630: AVideo before 29.1.0 Stored XSS via HTML Entity Bypass in trailer1 Field

> Attackers with upload permissions can inject malicious scripts via the trailer1 field, leading to arbitrary code execution and potential account takeover for visitors.

- **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
- **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:** 26 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-hv73-qqrq-m373, GHSA-v7vx-v9q9-qhw3

## What is CVE-2026-100630?

CVE-2026-100630 is a medium-severity cross-site scripting vulnerability in WWBN AVideo, published on 26 Sep 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

AVideo before 29.1.0 contains a stored cross-site scripting vulnerability in the video trailer1 field rendered unsanitized within an inline onclick JavaScript string. Attackers with video upload permission can store HTML entity-encoded payloads that bypass isValidURL() validation and are decoded by the browser to break out of the JavaScript string, executing arbitrary code in any visitor's session including administrators.

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

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


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

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

## Is CVE-2026-100630 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100630 is a medium-severity cross-site scripting vulnerability in WWBN AVideo, published on 26 Sep 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-100630 exists.

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

## Sources

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

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