CVE-2026-50183: WWBN AVideo Cross-Site Scripting Vulnerability

MODERATE
Advisory Identifier: GHSA-66q5-cj5g-wrfx
CVSS 4.7
CWE-79
Published
Advisory Summary

CVE-2026-50183 is a MODERATE (CVSS 4.7) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting WWBN AVideo libraries in the Packagist ecosystem. The issue involves stored xss via hostile youtube video title in avideo youtubeapi gallery section. Remediation is available in the latest vendor maintenance releases.

CVE-2026-50183 at a Glance

CVE Identifier CVE-2026-50183
GHSA Identifier GHSA-66q5-cj5g-wrfx
Severity MODERATE
CVSS v3.1 Base Score 4.7
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product WWBN AVideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-50183

To remediate this vulnerability, upgrade all affected WWBN AVideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

WWBN/AVideo fixed: Latest secure release
Upgrade WWBN/AVideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for WWBN/AVideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-50183, inspect your project dependencies for WWBN AVideo:

inspect dependencies for WWBN/AVideo

Analyze the terminal output to locate any version of WWBN AVideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In WWBN AVideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

# 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`: ```php // plugin/YouTubeAPI/YouTubeAPI.php (listVideos excerpt) $searchResponse = $youtube->search->listSearch( 'snippet,contentDetails,statistics', $options ); foreach ($searchResponse['items'] as $searchResult) { $vid = new YPTvideoObject( $searchResult["id"]["videoId"], $searchResult['snippet']["title"], // uploader-controlled $searchResult['snippet']["description"], $searchResult['snippet']["thumbnails"]["high"]["url"], $searchResult['snippet']["channelTitle"], "https://www.youtube.com/embed/{$searchResult['id']['videoId']}" ); $object->videos[] = $vid; } ``` `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: ```php // plugin/YouTubeAPI/gallerySection.php (foreach body) $youtubeTitle = $video->title; ... <a class="evideo" href="<?php echo $youtubeEmbedLink; ?>" title="<?php echo $youtubeTitle; ?>"> <!-- (i) attribute --> <img src="<?php echo $youtubeThumbs; ?>" alt="<?php echo str_replace('"', '', $youtubeTitle); ?>" ... /> <!-- (ii) attribute, partial --> </a> <a class="h6 evideo" href="<?php echo $youtubeEmbedLink; ?>" title="<?php echo $youtubeTitle; ?>"> <!-- (iii) attribute --> <h2><?php echo $youtubeTitle; ?></h2> <!-- (iv) element body --> </a> ``` Sites (i), (iii), and (iv) call no encoder. Site (ii) applies `str_replace('"', '', $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: ``` <script>alert(2222)</script> ``` 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: ``` https://avideo.example/ ``` Configure the YouTubeAPI plugin in the admin panel (`/plugins`) with any non-empty `developer_key` 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.

CVE-2026-50183 Affected WWBN AVideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
WWBN/AVideo
Packagist
≤ 29.0

References

Frequently Asked Questions

What is CVE-2026-50183?
CVE-2026-50183 is a security vulnerability in WWBN AVideo involving Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which WWBN AVideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: WWBN/AVideo.
What version fixes CVE-2026-50183?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is WWBN/AVideo affected?
Yes, WWBN/AVideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-50183?
CVE-2026-50183 has a CVSS v3.1 base score of 4.7 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-50183?
CVE-2026-50183 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for CVE-2026-50183?
Run the dependency tree command: 'inspect dependencies for WWBN/AVideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-66q5-cj5g-wrfx",
  "modified" : "2026-06-04T18:56:53Z",
  "published" : "2026-06-04T18:56:53Z",
  "aliases" : [ "CVE-2026-50183" ],
  "summary" : "WWBN AVideo: Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section",
  "details" : "# Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section\n\n## Summary\n\nA 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.\n\n## Details\n\n`plugin/YouTubeAPI/YouTubeAPI.php::listVideos()` fetches search results from the YouTube Data API and stores the `snippet.title` field unchanged inside a `YPTvideoObject`:\n\n```php\n// plugin/YouTubeAPI/YouTubeAPI.php (listVideos excerpt)\n$searchResponse = $youtube->search->listSearch(\n    'snippet,contentDetails,statistics', $options\n);\nforeach ($searchResponse['items'] as $searchResult) {\n    $vid = new YPTvideoObject(\n        $searchResult[\"id\"][\"videoId\"],\n        $searchResult['snippet'][\"title\"],          // uploader-controlled\n        $searchResult['snippet'][\"description\"],\n        $searchResult['snippet'][\"thumbnails\"][\"high\"][\"url\"],\n        $searchResult['snippet'][\"channelTitle\"],\n        \"https://www.youtube.com/embed/{$searchResult['id']['videoId']}\"\n    );\n    $object->videos[] = $vid;\n}\n```\n\n`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:\n\n```php\n// plugin/YouTubeAPI/gallerySection.php (foreach body)\n$youtubeTitle = $video->title;\n...\n<a class=\"evideo\" href=\"<?php echo $youtubeEmbedLink; ?>\" title=\"<?php echo $youtubeTitle; ?>\">          <!-- (i) attribute -->\n    <img src=\"<?php echo $youtubeThumbs; ?>\" alt=\"<?php echo str_replace('\"', '', $youtubeTitle); ?>\" ... />  <!-- (ii) attribute, partial -->\n</a>\n<a class=\"h6 evideo\" href=\"<?php echo $youtubeEmbedLink; ?>\" title=\"<?php echo $youtubeTitle; ?>\">       <!-- (iii) attribute -->\n    <h2><?php echo $youtubeTitle; ?></h2>                                                              <!-- (iv) element body -->\n</a>\n```\n\nSites (i), (iii), and (iv) call no encoder. Site (ii) applies `str_replace('\"', '', $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.\n\nAVideo 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.\n\n**Affected product:** AVideo (WWBN), YouTubeAPI plugin\n**Tested version:** master branch, commit 122b184 (snapshot dated 2026-05-22)\n\n## PoC\n\nThe 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:\n\n```\n<script>alert(2222)</script>\n```\n\nThe 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.\n\nAfter 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.\n\nFor 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:\n\n```\nhttps://avideo.example/\n```\n\nConfigure the YouTubeAPI plugin in the admin panel (`/plugins`) with any non-empty `developer_key` and any `keyword` value, then load the homepage. The browser fires `alert(2222)` as the gallery section finishes rendering.\n\n## Impact\n\nThis 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "WWBN/AVideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "29.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-66q5-cj5g-wrfx"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/7292129eaee5f609beae103b5cb387d55f17b877"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-04T18:56:53Z",
    "nvd_published_at" : null
  }
}