CVE-2026-54458: AVideo: Unauthenticated Stored DOM Cross-Site Scripting via Per-Client Metadata Broadcast in YPTSocket Plugin
WWBN AVideo is an open source video platform. Versions prior to 29.0 contain a stored DOM Cross-Site Scripting vulnerability in the YPTSocket plugin. Any unauthenticated remote attacker can execute arbitrary JavaScript in the authenticated origin of every administrator currently viewing a page that renders the YPTSocket online-users debug panel. plugin/YPTSocket/getWebSocket.json.php issues a signed WebSocket token to any anonymous caller, and MessageSQLiteV2::onOpen at plugin/YPTSocket/MessageSQLiteV2.php lines 91 and 110 reads the attacker-controlled webSocketSelfURI and page_title query parameters from the WebSocket connection URL with no validation. Both values persist into the in-memory SQLite connections table and broadcast inside the users_id_online array sent to every connected client; on the client, plugin/YPTSocket/script.js::updateSocketUserCard interpolates the broadcast page_title into an HTML template literal that is passed to jQuery $.append(html), which parses attacker bytes into live DOM nodes including <img> with inline event handlers. Successful attackers can can read non-HttpOnly cookies and the CSRF token rendered into the admin dashboard, issue authenticated requests to any admin-only endpoint, exfiltrate the admin dashboard DOM, and chain into any admin-context mutation. When the victim is an AVideo administrator, the attacker turns a single anonymous WebSocket connection into full administrative takeover via the admin's own session. This issue has been patched by https://github.com/WWBN/AVideo/commit/8be71e53ccbe9b84b30870db386fb4d2b11e1c16.
Security readout for executives and security teams
Plain-English summary
CVE-2026-54458 lets an unauthenticated attacker plant JavaScript that can run in an AVideo administrator’s browser when the YPTSocket online-users debug panel is viewed. In that admin context, the attacker may access page data and trigger admin-only actions through the victim’s session.
Executive priority
Treat this as urgent for any public or semi-public AVideo deployment with active administrators. The vulnerability starts without authentication and can lead to administrative takeover through a victim admin session, although current sources do not show known active exploitation.
Technical view
AVideo YPTSocket issued anonymous signed WebSocket tokens and stored unvalidated webSocketSelfURI and page_title values from connection URLs. Those values were broadcast to clients and page_title was inserted into DOM HTML via jQuery append, creating stored DOM XSS in the admin-viewed online-users debug panel.
Likely exposure
Exposure is limited to WWBN AVideo installations using vulnerable YPTSocket code, with sources listing versions prior to 29.0 and affected metadata listing <= 29.0. Risk is highest where administrators view the YPTSocket online-users debug panel.
Exploitation context
The source bundle reports a remote unauthenticated attack path, but successful impact requires an administrator to view a page rendering the vulnerable debug panel. KEV is false, and no cited source in the bundle confirms active exploitation.
Researcher notes
Key evidence is source-level: anonymous token issuance, unvalidated WebSocket query metadata, broadcast storage in users_id_online, and unsafe DOM insertion via updateSocketUserCard. There is a version ambiguity between “prior to 29.0” and “<= 29.0”; confirm exact fixed release from WWBN.
Mitigation direction
Apply the WWBN patch commit 8be71e53ccbe9b84b30870db386fb4d2b11e1c16.
Check the GitHub advisory for the fixed AVideo release guidance.
Restrict or disable the YPTSocket online-users debug panel until patched.
Limit administrator access to trusted networks where operationally feasible.
Review session and cookie hardening, especially for admin interfaces.
Validation and detection
Inventory all AVideo deployments and enabled YPTSocket plugin usage.
Verify whether the deployed code includes the referenced patch commit.
Confirm administrators can identify pages rendering the online-users debug panel.
Review WebSocket metadata logs for suspicious page_title or webSocketSelfURI values.
Test remediation only with non-malicious values in an authorized environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.