Quick answers
- Is CVE-2026-61569 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61569 being exploited in the wild.
- How severe is CVE-2026-61569?
- High severity, with a CVSS score of 7.5, published 28 October 2026.
- Which products and versions are affected?
- WWBN AVideo Encoder prior to 8.1.0.
- Is there a fix for CVE-2026-61569?
- Yes: fixed in 8.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61569 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61569?
- Check whether you run WWBN AVideo Encoder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 8.1.0
Technical details
The vulnerability is a SQL injection in the `Streamer::get` function within `objects/Streamer.php`, where the `user` parameter from the unauthenticated `/objects/login.json.php` endpoint is interpolated directly into a SELECT query without parameterization. Although single quotes are stripped by `security.php`, HTML entity decoding in `Login.php` restores them before query execution. An attacker can inject UNION-based SQL queries to read arbitrary database data; results are exposed via the `streamers_id` response field or query error messages. Successful exploitation requires bypassing the streamer allowlist (which is empty by default, allowing all sites) and having the login response set `canUpload` or `isAdmin`.
Affected products
- WWBN AVideo Encoder prior to 8.1.0
Timeline
- 2026-10-28: disclosed