CVE-2026-49279 WWBN AVideo: Stored XSS via autoEvalCodeOnHTML Bypass in MessageSQLite WebSocket Handler (CVE-2026-43874 Bypass)
Authenticated attackers can execute arbitrary JavaScript via WebSocket messages, leading to session hijacking and account takeover in the AVideo platform.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-49279?
CVE-2026-49279 is a high-severity cross-site scripting vulnerability in WWBN AVideo, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
WWBN AVideo is an open source video platform. Versions 29.0 and below contain a Stored XSS vulnerability through the autoEvalCodeOnHTML parameter in the MessageSQLite WebSocket Handler. The MessageSQLite.php handler only strips autoEvalCodeOnHTML from $json['msg'], but msgToResourceId() reads from $msg['json'] with higher priority. An attacker can place the XSS payload in the json key instead of msg, bypassing the sanitization entirely. An authenticated attacker can execute arbitrary JavaScript in any connected user's browser session via the WebSocket messaging system, stealing session cookies and authentication tokens, taking over accounts through session hijacking, and chaining with CSRF to perform admin actions on the victim's behalf, in the default SQLite WebSocket backend configuration. This issue has a patch that has yet to be officially released, see https://github.com/WWBN/AVideo/commit/3e0b3ce2bfa766183ff0ae227439394db57b1a23.
Weakness: CWE-79
Which versions are affected by CVE-2026-49279?
2 open source packages ship an affected version, including wwbn/avideo.
| Package | Affected | Fixed in |
|---|---|---|
wwbn/avideo Packagist | All versions to 29.0 | None |
wwbn/avideo Packagist | All versions to 29.0 | None |
How do I fix CVE-2026-49279?
No fix has been published for CVE-2026-49279 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-49279 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49279 exists.
Sources
Also known as GHSA-2fhx-q92v-5fhv.