# CVE-2026-61575: AVideo-Encoder vulnerable to stored DOM cross-site scripting through queue titles


- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-w2g8-p296-r5g9

## What is CVE-2026-61575?

CVE-2026-61575 is a medium-severity vulnerability in WWBN AVideo-Encoder, published on 28 Oct 2026. 

### Official description

AVideo is a video-sharing Platform. Prior to 8.1.0, `view/queue.php` uses `pathinfo` on the caller-controlled `fileURI` and stores its filename through `setTitle` in `encoder_queue.title` without neutralization. `fileURI` is not in the `objects/security.php` filter lists, and the `Login::canUpload()` capability needed to submit a queue entry can be self-granted using an attacker-controlled login site without legitimate encoder credentials. `view/index.php` loads `queue.json` from `view/queue.json.php` into the `#grid` jQuery Bootgrid table; its title formatter concatenates `row.title` into raw cell HTML. An attacker can therefore store an HTML title whose event handler runs in a privileged viewer's browser. `Encoder::getAll` limits nonadministrators to their own streamer's rows, so the victim must be an administrator who sees all rows or an operator on the attacker's streamer. A second `.html()` sink in the progress panel uses the same title but additionally depends on a helper script loaded from the streamer; the Bootgrid sink is reachable from encoder code alone. The script can read session-visible data and rendered streamer credentials, act with the viewer's privileges, and execute again for each qualifying viewer until the row is removed. This issue is fixed in version 8.1.0.

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

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


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

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

## Is CVE-2026-61575 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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