CVE-2026-50183 is a medium-severity cross-site scripting (XSS) vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet.
Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section Summary A stored Cross-Site Scripting vulnerability (CWE-79; chained CWE-829, Inclusion of Functionality from Untrusted Control Sphere) in the AVideo YouTubeAPI plugin renders the snippet.title field returned by the YouTube Data API into the homepage gallery markup with no HTML encoding. The title is set by the YouTube video uploader (anyone in the world) and is treated by AVideo as trusted content. A YouTube uploader who controls a video matching the operator's configured query injects HTML into the AVideo homepage by setting their video's title to a JavaScript-bearing string; the payload then executes in the browser of every visitor who loads any page that renders the gallery. Details plugin/YouTubeAPI/YouTubeAPI.php::listVideos() fetches search results from the YouTube Data API and stores the snippet.title field unchanged inside a YPTvideoObject: plugin/YouTubeAPI/gallerySection.php then renders the title into three HTML contexts inside each gallery card. Four reflection sites total, three of them completely unprotected: Sites (i), (iii), and (iv) call no encoder. Site (ii) applies strreplace('"', '', $youtubeTitle) which strips quotes from one attribute and leaves the other three reflections untouched. The strongest sink is (iv) at line 60: a title containing <script>alert(2222)</script> produces <h2><script>alert(2222)</script></h2> in the rendered DOM, which the browser parses as a live script element and executes synchronously. The single half-mitigation at line 57 is the maintainer's evidence of awareness of the attribute-injection risk; the same developer left the other three sinks unprotected. AVideo additionally caches the YouTube response for cacheTimeout seconds (default 3600), so even after the title is changed on YouTube or the video is removed, the AVideo gallery continues to serve the malicious title until the cache expires or is manually flushed. Affected product: AVideo (WWBN), YouTubeAPI plugin Tested version: master branch, commit 122b184 (snapshot dated 2026-05-22) PoC The AVideo operator must have the YouTubeAPI plugin enabled (the default after configuring a YouTube Data API key) with showGallerySection=true (the default). The attacker controls a YouTube video (uploaded under any free YouTube account) whose title is set to: The attacker arranges for the AVideo operator's configured YouTube search query (the keyword plugin setting, typically a channel name or topical phrase) to match the hostile video. The matching condition is the same as a normal YouTube search: a unique phrase in the video's description, a channel name the operator follows, or any query the operator has configured. After AVideo's cacheTimeout window elapses (default 3600 seconds) and a fresh listVideos() call fetches the malicious title, any visitor opening the AVideo homepage triggers an alert(2222) modal dialog as the gallery card renders. For deterministic test reproduction, deploy a mock YouTube Data API service that impersonates www.googleapis.com and youtube.googleapis.com on the AVideo Docker network and returns the malicious title directly. The PoC then reduces to: Configure the YouTubeAPI plugin in the admin panel (/plugins) with any non-empty developerkey and any keyword value, then load the homepage. The browser fires alert(2222) as the gallery section finishes rendering. Impact This is a Stored XSS vulnerability (CWE-79) in a publicly-rendered HTML context, with the data source under attacker control (CWE-829). Every visitor who loads any AVideo page rendering the YouTubeAPI gallery section is impacted: the injected JavaScript runs in the visitor's session under the AVideo origin, reads non-HttpOnly cookies, and issues authenticated requests as the visitor. When the visitor is an AVideo administrator, the injected JavaScript performs any admin action (create user, promote to admin, change configuration, install plugin) that uses cookie-based authentication without an additional CSRF token, escalating the bug into full administrative takeover. The payload persists for the duration of cacheTimeout (default 3600 seconds) after the malicious title is set on YouTube and survives YouTube removing the hostile video for the same window.
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-50183 has a CVSS score of 4.7 (Medium). 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-50183 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-50183 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-50183 in your environment →No fixed version is listed for CVE-2026-50183 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-50183 is a medium-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-50183 has a CVSS score of 4.7 (Medium). 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-50183 yet. Monitor the advisory for updates and apply mitigations in the interim.
Whether CVE-2026-50183 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.