On this page (7 sections)

A critical vulnerability, tracked as CVE-2026-130650, affects WWBN AVideo, the open source video platform. According to the GitHub Advisory Database entry, the default node socket server relays a message field called autoEvalCodeOnHTML without a filter that is meant to keep it PHP-only. An unauthenticated attacker can use that gap to run script in an administrator's browser.

If you host AVideo, especially with the bundled socket server running, treat this as urgent. The advisory lists no patched version yet, so the practical work right now is exposure checking and reducing access to the socket service.

What happened

The vulnerability was published on November 18, 2026 in the GitHub Advisory Database, which links to the NVD record and to a project advisory, GHSA-vw5g-hfpm-2m4g. The GitHub entry is marked unreviewed, lists no package, and gives affected and patched versions as unknown. The NVD text is the same description, so it is not separate confirmation.

Only one source of technical detail exists so far. We have not seen vendor release notes, a fixed release, or reports of attacks, so details may change as the project responds.

How the weakness works

AVideo includes a node-based socket server that pushes real-time messages between the server and connected browsers. The advisory says this server forwards a field named autoEvalCodeOnHTML to clients without applying the filter that is supposed to restrict it to PHP-originated messages. In plain terms, the server trusts a message field that outside parties should never be able to set.

Per the advisory, an unauthenticated attacker can obtain an anonymous socket token, then send a spoofed MSG_BATCH message. Administrators' browsers that receive it call eval() on the supplied content, which runs attacker-chosen script in the context of the admin session. The advisory states the result can be account takeover.

This is a cross-site scripting issue delivered through a messaging channel rather than a web form. The CVSS v4 metrics in the advisory reflect that: network attack vector, low complexity, no privileges, no user interaction, and high confidentiality and integrity impact on the vulnerable system.

Who is exposed

  • Sites running WWBN AVideo at or before the commit named in the advisory, with the default node socket server enabled and reachable.
  • Installations where administrators stay logged in to the AVideo admin area in a browser while the socket connection is active. The advisory describes the attack as hitting administrators' browsers.
  • Hosting providers and agencies managing AVideo instances for clients.

The research does not say whether installations without the socket server are affected, or how many instances are reachable online. If you are unsure whether the socket server is running, assume exposure until you confirm otherwise.

How to check your exposure

These are read-only checks. First, find out whether a node process is running on the server and which ports it listens on. Run this on the AVideo host and look for a node process bound to a public interface.

List listening TCP sockets and owning processes on the AVideo host (Linux, run as root)Shell
ss -tlnp | grep -i node

Next, record which AVideo code you run. If you installed from a git checkout, this prints the current commit so you can compare it with the one named in the advisory (c3edcc274c389816d434acadac07ee78eaf330c1). Run it in the AVideo directory.

Show the checked-out AVideo commit (run in the AVideo install directory)Shell
git log -1 --format=%H

Because no fixed version is published, being on a newer commit than the one named is not proof of a fix unless the project says so. Watch the project advisory for updates.

What to do now

Caution. Stopping or firewalling the socket server may disable real-time features such as live notifications on your AVideo site. Test on a staging copy if you can, and make the change during a quiet period.
  1. Identify every AVideo instance you run and whether the node socket server is enabled.
  2. Restrict network access to the socket server port with your host firewall or reverse proxy so only trusted sources can reach it, or disable the socket server if you do not need it.
  3. Watch the AVideo project advisory and repository for a fix, and update as soon as one is released.
  4. Ask administrators to log out of the AVideo admin area when not in use and avoid browsing the admin panel while the socket service is exposed.
  5. Rotate administrator passwords and review the admin user list for accounts you do not recognize.
  6. Review web server and socket server logs for unusual connection patterns from unknown clients around and after November 18, 2026.
  7. Keep a backup of your database and files so you can recover if an admin account was abused.
Tip. A web application firewall in front of the site can add a layer of filtering, but it will not necessarily inspect a separate socket port. Do not rely on it as a substitute for restricting access or applying the vendor fix. See what a WAF is for what these tools cover.

Detection and monitoring afterwards

Since the attack runs in an admin's browser, signs of abuse may look like legitimate admin activity. Check for new administrator accounts, changed settings, unexpected plugins or modified files, and review your admin login history. If you suspect a takeover, follow the steps in website hacked: what to do.

For ongoing visibility, Webforta Monitor can alert you to uptime, certificate, DNS and header changes, which helps spot tampering with a public site, and the free malware scanner gives an outside-in check. Neither is a fix for this flaw, and outside tools cannot see what happens inside an admin's browser session.

Open questions

  • No patched version or release is listed in the advisory.
  • The GitHub entry is unreviewed, and affected versions are stated only as 'through' a specific commit.
  • No public reports of exploitation appear in the research, but the advisory describes an attack requiring no authentication, so do not wait for such reports before acting.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130650 - GitHub Advisory Databasegithub.com
  2. CVE-2026-130650: WWBN AVideo through c3edcc274c389816d434acadac07ee78eaf330c1 contains a cross-site scripting vulnerability because the default node socket server relays…nvd.nist.gov ·
  • AVideo
  • XSS
  • CVE-2026-130650
  • WebSocket
  • Video platform