# CVE-2026-61569: AVideo-Encoder: pre-authentication streamer-login SQL injection


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-2rrq-xf8q-3qpf

## What is CVE-2026-61569?

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

### Official description

AVideo is a video-sharing Platform. Prior to 8.1.0, the unauthenticated streamer login at `objects/login.json.php` passes the `user` parameter to `Streamer::get` in `objects/Streamer.php`, where it is interpolated into a single-quoted MariaDB SELECT without parameterization or escaping. Although `objects/security.php` strips literal single quotes, `html_entity_decode` in `objects/Login.php` restores entity-encoded quotes before the query. The supplied `siteURL` must pass the streamer allowlist, which allows all sites when empty by default, and an attacker-hosted login response must set `canUpload` or `isAdmin` to reach `Streamer::createIfNotExists`. That function calls `Streamer::get` before its additional allowlist check. UNION results are exposed through `streamers_id`, while failures return the rendered query and MariaDB error. An attacker can read arbitrary encoder database data, including stored upstream streamer credentials, allowlist configuration, and queue records, without encoder credentials. Stacked statements are not permitted by the mysqli driver and the tested database account lacks global FILE privilege, so the demonstrated vector is bounded to reads rather than server-side file writes. Stolen streamer credentials can provide continued upstream access until rotated. This issue is fixed in version 8.1.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-61569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61569 is a high-severity vulnerability in WWBN AVideo-Encoder, published on 28 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61569 exists.

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

## Sources

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

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