WWBN AVideo: Stored XSS via autoEvalCodeOnHTML Bypass in MessageSQLite WebSocket Handler (CVE-2026-43874 Bypass)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-49279: 0.40% estimated exploitation activity in the next 30 days; percentile 34.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

AVideo: Stored XSS via autoEvalCodeOnHTML in MessageSQLite WebSocket Handler Summary AVideo has a stored XSS vulnerability in the WebSocket messaging system. 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. Affected Versions AVideo <= latest Vulnerability Details Root Cause: Shallow sanitization only covers $json['msg'] plugin/YPTSocket/MessageSQLite.php lines 268-271 — the incomplete fix: plugin/YPTSocket/MessageSQLite.php lines 361-367 — the bypass via msgToResourceId(): Compare with the correctly patched Message.php (lines 254-256): And MessageSQLiteV2.php (lines 302-303): MessageSQLite.php does not call removeAutoEvalCodeOnHTMLRecursive() at all. Attack Chain - Attacker sends a WebSocket message with autoEvalCodeOnHTML in the json key instead of msg - The fix at line 268-271…

Published by the source

4 Jun 2026, 18:55 UTC

Last modified by the source

4 Jun 2026, 18:55 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2fhx-q92v-5fhv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-49279

Advisory: WWBN AVideo: Stored XSS via autoEvalCodeOnHTML Bypass in MessageSQLite WebSocket Handler (CVE-2026-43874 Bypass)
IDs: CVE-2026-49279, GHSA-2fhx-q92v-5fhv
Record: https://patchnext.com/advisories/cve-2026-49279 (revision 1, source checked 26 Oct 2026, 14:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected <= 29.0

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2fhx-q92v-5fhv (GitHub-reviewed advisory GHSA-2fhx-q92v-5fhv lists affected ranges: Packagist wwbn/avideo >=0 <=29.0)

Commands are suggestions: review each one before running it.