How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

352,262

Total vulnerabilities in the database

CVE-2026-54458 — wwbn / avideo

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Unauthenticated Stored DOM XSS via `page_title` 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 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.

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:

// plugin/YPTSocket/functions.php:21-24
if (!empty($_REQUEST[&#039;webSocketSelfURI&#039;])) {
    $msgObj-&gt;selfURI = $_REQUEST[&#039;webSocketSelfURI&#039;];
} else {
    $msgObj-&gt;selfURI = getSelfURI();
}

On WebSocket open, MessageSQLiteV2::onOpen reads webSocketSelfURI and page_title from the connection URL query string and persists both verbatim into the in-memory SQLite connections table:

// plugin/YPTSocket/MessageSQLiteV2.php:91 and :110
$client[&#039;selfURI&#039;]    = $wsocketGetVars[&#039;webSocketSelfURI&#039;];        // line 91
$client[&#039;page_title&#039;] = @utf8_encode(@$wsocketGetVars[&#039;page_title&#039;]); // line 110

utf8_encode 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 users_id_online, 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 page_title into an HTML template literal and passes the result to jQuery $.append(html):

// plugin/YPTSocket/script.js:685-691
if (userData.page_title) textParts.push(userData.page_title);
const finalText = textParts.join(&#039; &#039;);
const html = `&lt;a href=&quot;${selfURI}&quot; target=&quot;_blank&quot; ...&gt;
                &lt;i class=&quot;far fa-compass&quot;&gt;&lt;/i&gt; ${finalText}
              &lt;/a&gt;`;
$(`#${socketUserDivID} .socketUserPages`).append(html);  // sink

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:

(async () =&gt; {
  const PAYLOAD = &#039;&lt;img src=q onerror=&quot;document.body.style.backgroundColor=String.fromCharCode(114,101,100);document.title=String.fromCharCode(80,87,78,69,68)&quot;&gt;&#039;;
  const r = await fetch(&#039;/plugin/YPTSocket/getWebSocket.json.php?webSocketSelfURI=&#039; + encodeURIComponent(&#039;/dashboard?x=1&#039;));
  const j = await r.json();
  const u = j.webSocketURL
          + &#039;&amp;webSocketSelfURI=&#039; + encodeURIComponent(&#039;/dashboard?x=1&#039;)
          + &#039;&amp;page_title=&#039;       + encodeURIComponent(PAYLOAD);
  const ws = new WebSocket(u);
  ws.onopen    = () =&gt; console.log(&#039;attacker connected&#039;);
  ws.onmessage = e =&gt; console.log(&#039;attacker frame:&#039;, e.data.slice(0, 200));
})();

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 page_title. 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.

Published: Jun 4, 2026
Updated: Jun 23, 2026
CVE: CVE-2026-54458
GHSA: GHSA-8whc-2wmv-ww35
Severity: Critical
Exploit:
CISA KEV:

CVSS v3:

Severity: Critical
Score: 9.6
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L

CWEs:

CWE-79

OWASP TOP 10:

A7 - Cross-Site Scripting (XSS)

Affected Software
References

Software	From	Fixed in
wwbn / avideo	-	29.0.x

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.