CVE-2026-50182 is a medium-severity cross-site scripting (XSS) vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet.
Unauthenticated Reflected XSS via $GET['search'] in AVideo YouTubeAPI Gallery Pagination Summary A reflected Cross-Site Scripting vulnerability (CWE-79) in the AVideo YouTubeAPI plugin allows any unauthenticated attacker to execute arbitrary JavaScript in a victim's browser session when the victim follows a crafted URL. The $GET['search'] query parameter is concatenated directly into the href attribute of two pagination links in plugin/YouTubeAPI/gallerySection.php (lines 67 and 74) with no htmlspecialchars, no urlencode, and no allow-list check. An injected <script> element is then extracted by the AVideo Layout plugin and concatenated into a single trailing inline script block at the bottom of the page, where the browser executes it. Details plugin/YouTubeAPI/gallerySection.php renders the YouTubeAPI plugin's gallery section on the AVideo homepage (and every page that includes plugin/Gallery/view/mainArea.php) when the API plugin is enabled with showGallerySection=true (the default). The pagination block at lines 67 and 74 builds the previous-page and next-page <a> elements by string-interpolating $GET['search'] directly: The @ operator only suppresses an undefined-index warning; it does not sanitize the value. A payload like "><script>alert(1337)</script> closes the href attribute, closes the <a> element, and injects a fresh <script> tag. Two preconditions gate the sink. First, the YouTube API call must return a pagination token (always true for any non-trivial result set, since the mock or real YouTube response carries nextPageToken for multi-page queries). Second, plugin/Gallery/view/mainArea.php line 53 wraps the gallery render in if (!empty($video)) { echo AVideoPlugin::getGallerySection(); } else { / output captured and discarded / }. When $GET['search'] is set, Video::getVideo() adds a MySQL fulltext MATCH(v.title) AGAINST (<search>) IN NATURAL LANGUAGE MODE clause; the payload tokenizes to words like script, alert, 1337, and the gate passes whenever any video in the corpus has a title containing one of those words. Realistic deployments overwhelmingly satisfy this; the attacker can also seed the payload with a common word (?search=video"><script>...</script>) to guarantee a fulltext hit. The AVideo Layout plugin (plugin/Layout/Layout.php:611, enabled by default) runs Layout::organizeHTML() over the final HTML, extracts every inline <script[^>]>(.)</script> block via regex, and concatenates their inner contents into one trailing <script> block placed immediately before </body>. The injected <script>alert(1337)</script> is therefore moved out of the original href context and into a clean executable script block; the visible pagination markup retains only the leftover &search="> bytes. Affected product: AVideo (WWBN), API + YouTubeAPI + Layout plugins Tested version: master branch, commit 122b184 (snapshot dated 2026-05-22) PoC The AVideo deployment must have the YouTubeAPI plugin enabled with the default showGallerySection=true. The payload also needs to satisfy the fulltext MATCH(v.title) AGAINST gate that Video::getVideo() adds when $_GET['search'] is set: at least one video in the corpus must have a title containing one of the payload's tokens. In the live confirmation a video titled Tutorial about script error alerts satisfied the gate via the words script and alert. Seeding the payload with the common word video guarantees a hit on any realistic AVideo deployment, since video appears in nearly every video title. Open the following URL in any browser. No authentication, no session cookie, no prior interaction with the site is required: The browser fires an alert(1337) modal dialog as soon as the homepage finishes rendering. The injected <script> is no longer inside the href markup at render time; it lives inside the page's single trailing inline script block, surfaced there by the Layout plugin's HTML reorganization. Impact This is a Reflected XSS vulnerability (CWE-79) on the AVideo public homepage. Any unauthenticated remote attacker who induces a victim to follow a crafted URL executes arbitrary JavaScript in the victim's browser session under the AVideo origin, reading non-HttpOnly cookies and issuing authenticated AJAX requests as the victim. When the victim 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 a single click on a crafted link into full administrative takeover.
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-50182 has a CVSS score of 6.1 (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-50182 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-50182 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-50182 in your environment →No fixed version is listed for CVE-2026-50182 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-50182 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-50182 has a CVSS score of 6.1 (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-50182 yet. Monitor the advisory for updates and apply mitigations in the interim.
Whether CVE-2026-50182 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.