CVE
AVideo cross-site scripting in YPTSocket socket server
Affects AVideo through c3edcc274c when the default node socket server (socketIO=true) is in use, where anonymous visitors can reach the relay. No fixed version or patch ids are given in the checked facts.
- Exploited
- Proof of concept public, per CISA
- Fix
- See vendor advisory
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
WWBN AVideo contains a cross-site scripting flaw in its default socket server, which passes along HTML-related code without the PHP-only filter. Remote attackers can connect without logging in, send a spoofed message that runs code in administrators' browsers, and take over their accounts.
Original description
WWBN AVideo through c3edcc274c389816d434acadac07ee78eaf330c1 contains a cross-site scripting vulnerability because the default node socket server relays autoEvalCodeOnHTML without the PHP-only filter. Unauthenticated attackers can obtain an anonymous socket token and send a spoofed MSG_BATCH message to trigger client eval() in administrators' browsers for account takeover.
Who should check
Teams running WWBN AVideo at or before c3edcc274c with YPTSocket and the default node socket server (socketIO=true)
Not fixed by: Fixes in the PHP socket handlers do not cover the default node socket server.
“plugin/YPTSocket/YPTSocket.php:136 sets $obj->socketIO = true”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure25/25Default setups, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Workaround: The checked facts name no workaround. Limiting the affected feature would mean the default node socket server (socketIO=true), but the facts do not say how to disable or restrict it safely.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130650 (AVideo through c3edcc274c YPTSocket XSS via MSG_BATCH autoEvalCodeOnHTML Spoof), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130650 (entry last updated 2026-11-18):
Affected:
- WWBN AVideo: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Default node socket server (socketIO=true) in AVideo through c3edcc274c (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-vw5g-hfpm-2m4g)
- Attacker obtains an anonymous socket token, which the advisory says is minted for visitors without login (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-vw5g-hfpm-2m4g)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130650 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130650 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/WWBN/AVideo/security/advisories/GHSA-vw5g-hfpm-2m4g
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130650
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130650"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- WWBN AVideo
Version range not reported
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · WWBN/AVideo · Advisory GHSA-vw5g-hfpm-2m4g |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130650 |
| Record | NVD · CVE-2026-130650 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130650
Is CVE-2026-130650 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The socket server still relays the autoEvalCodeOnHTML message through MSG_BATCH, which can run arbitrary JavaScript in the origin of connected clients. The advisory says this can include administrators and enable full administrative takeover.Source: github.com
Am I affected, and how do I check?
AVideo through c3edcc274c with the default node socket server (socketIO=true). The advisory describes the attack path as starting from an anonymous socket token, which it says is issued to visitors without login. A reader can check whether the socket server is enabled by looking at the socketIO setting in the AVideo configuration.Source: github.com
How do I fix CVE-2026-130650?
The checked facts name no fixed version and no vendor patch ids for this vulnerability. The advisory describes the earlier fix as incomplete, so check the vendor's advisory for an updated fix before relying on any version.Source: github.com
What if there's no patch?
The checked facts name no workaround. Limiting the affected feature would mean the default node socket server (socketIO=true), but the facts do not say how to disable or restrict it safely.Source: github.com