dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-49279

HIGH · 7.7 CVSS v4.0 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in AVideo's MessageSQLite WebSocket handler where autoEvalCodeOnHTML parameter sanitization only strips the payload from $json['msg'], but msgToResourceId() processes $msg['json'] with higher priority, allowing attackers to bypass sanitization by placing XSS in the json key instead.

MitigationApply the pending patch from commit 3e0b3ce to sanitize both $json['msg'] and $msg['json']; until patch is released, disable or restrict the WebSocket messaging feature and limit authenticated user privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify AVideo installation
    Locate the AVideo web application directory and check for the presence of MessageSQLite.php in the plugin or websocket directories
    Affected if AVideo platform is present with MessageSQLite WebSocket functionality
  2. Verify WebSocket messaging is enabled
    Check the AVideo configuration or plugin settings for WebSocket messaging functionality status
    Affected if WebSocket messaging feature is enabled in the AVideo configuration
  3. Check AVideo version
    Look for a version file or check the main AVideo index.php for the version number, then compare against any known vulnerable version range
    Affected if Installed version falls within a vulnerable range if such a range is documented by AVideo
  4. Inspect MessageSQLite.php for the sanitization flaw
    Examine the MessageSQLite.php file in the WebSocket handler directory; look for the autoEvalCodeOnHTML parameter handling and verify if $json['json'] is processed without sanitization while $json['msg'] is sanitized
    Affected if The code shows $json['msg'] is sanitized but $json['json'] is processed without sanitization in msgToResourceId() function
  5. Confirm autoEvalCodeOnHTML is active
    Check the WebSocket configuration or MessageSQLite settings to see if autoEvalCodeOnHTML is enabled
    Affected if autoEvalCodeOnHTML is enabled and the vulnerable sanitization bypass exists

A user is affected if they run AVideo with the MessageSQLite WebSocket handler where autoEvalCodeOnHTML is enabled and the code processes $json['json'] without the same sanitization applied to $json['msg'].

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply the pending patch from commit 3e0b3ce to sanitize both $json['msg'] and $msg['json']; until patch is released, disable or restrict the WebSocket messaging feature and limit authenticated user privileges.

Recommended fix High confidence
  1. Navigate to the AVideo repository at https://github.com/WWBN/AVideo
  2. Locate the file MessageSQLite.php in the WebSocket handlers directory
  3. Apply the patch from commit 3e0b3ce2bfa766183ff0ae227439394db57b1a23 to fix the sanitization bypass
  4. Ensure the fix properly handles the json key in addition to the msg key for autoEvalCodeOnHTML parameter
  5. After applying the patch, restart any running WebSocket services to load the updated code
  6. Verify the fix by testing that XSS payloads in the json key are properly sanitized

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49279 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data