# CVE-2026-50182: AVideo Has Unauthenticated Reflected XSS via $_GET['search'] in YouTubeAPI Gallery Pagination

> Unauthenticated attackers can execute arbitrary JavaScript via reflected XSS in AVideo, potentially leading to full administrative takeover if the victim is an admin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-hgjh-6wj8-gcgf

## What is CVE-2026-50182?

CVE-2026-50182 is a medium-severity cross-site scripting vulnerability in WWBN AVideo, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

WWBN AVideo is an open source video platform. Versions prior to 29.0 contain an unauthenticated Reflected XSS vulnerability through AVideo YouTubeAPI Gallery Pagination. 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.  Any unauthenticated attacker can lure a victim into following a crafted URL to execute arbitrary JavaScript under the AVideo origin, which can read non-HttpOnly cookies and issue authenticated AJAX requests as the victim, and when the victim is an administrator, it can perform any cookie-authenticated admin action (create user, promote to admin, change configuration, install plugin), escalating a single click into full administrative takeover. This issue has been patched by this commit: https://github.com/WWBN/AVideo/commit/f50fc033b7adb36f1ffd6640e7826468bdafdec3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-50182?

2 open source packages ship an affected version, including WWBN/AVideo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `WWBN/AVideo` | Packagist | All versions to 29.0 | None |
| `WWBN/AVideo` | Packagist | All versions to 29.0 | None |

## How do I fix CVE-2026-50182?

No fix has been published for CVE-2026-50182 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-50182 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50182 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50182 and fix it if it is affected.

What it is: CVE-2026-50182 is a medium-severity cross-site scripting vulnerability in WWBN AVideo, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50182 exists.

Affected packages and fixed versions:
- WWBN/AVideo (Packagist): affected all versions up to 29.0; no fix listed
- WWBN/AVideo (Packagist): affected all versions up to 29.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50182/ (Markdown: https://insights.sbomify.com/CVE-2026-50182/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50182
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50182
- OSV: https://osv.dev/vulnerability/CVE-2026-50182

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50182/
Summaries are generated and may contain mistakes; the official description above is the record.