CVE-2026-54458 is a critical-severity cross-site scripting (XSS) vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet.
Unauthenticated Stored DOM XSS via pagetitle Broadcast in AVideo YPTSocket Plugin Summary A stored DOM Cross-Site Scripting vulnerability (CWE-79) in the AVideo YPTSocket plugin lets any unauthenticated remote attacker 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 pagetitle query parameters from the WebSocket connection URL with no validation. Both values persist into the in-memory SQLite connections table and broadcast inside the usersidonline array sent to every connected client; on the client, plugin/YPTSocket/script.js::updateSocketUserCard interpolates the broadcast pagetitle 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. Details plugin/YPTSocket/getWebSocket.json.php issues a WebSocket token to any caller; the only gate is AVideoPlugin::isEnabledByName("YPTSocket"). The token-issuance helper getEncryptedInfo() at plugin/YPTSocket/functions.php:21-24 writes $REQUEST['webSocketSelfURI'] directly into the per-token state without validation: On WebSocket open, MessageSQLiteV2::onOpen reads webSocketSelfURI and pagetitle from the connection URL query string and persists both verbatim into the in-memory SQLite connections table: utf8encode is not an HTML encode. The broadcast helper dbGetUniqueUsers() (plugin/YPTSocket/db.php:288-300) selects both columns without escape and returns them as part of usersidonline, which msgToResourceId() at MessageSQLiteV2.php:444 places in the outbound JSON frame sent to every connected client. JSON encoding escapes " to \" for transport, but the receiving browser's JSON.parse(event.data) reverses the escape and restores the raw HTML bytes before they reach script.js. On the client, plugin/YPTSocket/script.js::updateSocketUserCard (lines 638 to 700) interpolates the broadcast pagetitle into an HTML template literal and passes the result to jQuery $.append(html): jQuery's .append(html) parses the string with the browser HTML parser, building live DOM nodes for any tag the attacker supplied, including <img> with inline event handlers. The browser's load attempt on the attacker-supplied src fails and the inline onerror event handler fires synchronously inside the admin's authenticated origin. The victim precondition is that the YPTSocket online-users debug panel (#socketUsersURI) is rendered in the admin's DOM. plugin/YPTSocket/footer.php:12 renders the panel when User::isAdmin() && !empty($obj->debugSocket). The debugSocket plugin flag is true by default after enable, so any admin viewing any logged-in AVideo page with the standard YPTSocket footer holds a live broadcast subscription. Affected product: AVideo (WWBN), YPTSocket plugin Tested version: master branch (snapshot dated 2026-05-22) PoC The AVideo deployment must have the YPTSocket plugin enabled (the default after enable) with debugSocket=true (the default), and at least one administrator must currently be viewing a page that loads the YPTSocket footer (any logged-in AVideo page does). The attacker requires only network reachability to getWebSocket.json.php over HTTPS and to the WebSocket TLS port. Open DevTools Console on any browser tab pointed at the AVideo origin and paste the following one-liner. No authentication and no session cookie are required for the attacker side: The payload uses String.fromCharCode to spell its side-effect strings (String.fromCharCode(114,101,100) decodes to red; String.fromCharCode(80,87,78,69,68) decodes to PWNED) so no quote, backtick, or backslash bytes appear in transit. Within one server broadcast cycle, every administrator tab currently rendering the YPTSocket debug panel turns its page background red and changes its browser tab title to PWNED. Both side-effects are produced by attacker JavaScript executing inside the admin's authenticated AVideo origin. Impact This is a stored DOM Cross-Site Scripting vulnerability (CWE-79) in the AVideo YPTSocket plugin. An unauthenticated remote attacker who can reach the YPTSocket endpoints plants the payload by issuing one anonymous HTTP GET to getWebSocket.json.php followed by one anonymous WebSocket frame carrying the malicious pagetitle. The attacker JavaScript executes inside the admin's authenticated AVideo origin and 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.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2026-54458 has a CVSS score of 9.6 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
composer
WWBN/AVideo (<= 29.0)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-54458 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-54458 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-54458 in your environment →No fixed version is listed for CVE-2026-54458 yet.
In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-54458 is a critical-severity cross-site scripting (XSS) vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
CVE-2026-54458 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
WWBN/AVideo (composer) versions <= 29.0 is affected.
No fixed version is listed for CVE-2026-54458 yet. Monitor the advisory for updates and apply mitigations in the interim.
Whether CVE-2026-54458 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.