# CVE-2026-33238: AVideo has a Path Traversal in listFiles.json.php that Enables Server Filesystem Enumeration

> An authenticated uploader can enumerate server files via path traversal in listFiles.json.php, exposing private media paths.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-4wmm-6qxj-fpj4

## What is CVE-2026-33238?

CVE-2026-33238 is a medium-severity path traversal vulnerability in Wwbn Avideo, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. Prior to version 26.0, the `listFiles.json.php` endpoint accepts a `path` POST parameter and passes it directly to `glob()` without restricting the path to an allowed base directory. An authenticated uploader can traverse the entire server filesystem by supplying arbitrary absolute paths, enumerating `.mp4` filenames and their full absolute filesystem paths wherever they exist on the server — including locations outside the web root, such as private or premium media directories. Version 26.0 contains a patch for the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including wwbn/avideo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions | 26.0 |
| `wwbn/avideo` | Packagist | All versions | 26.0 |

Products: Wwbn Avideo.

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

Upgrade wwbn/avideo to 26.0 or later.

## Is CVE-2026-33238 being exploited?

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

## Other vulnerabilities in Wwbn Avideo

- [CVE-2026-40911](https://insights.sbomify.com/CVE-2026-40911/): WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks (critical 10.0)
- [CVE-2026-33478](https://insights.sbomify.com/CVE-2026-33478/): AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection (critical 10.0)
- [CVE-2022-30534](https://insights.sbomify.com/CVE-2022-30534/): Command injection in AVideo (critical 9.9)
- [CVE-2022-30547](https://insights.sbomify.com/CVE-2022-30547/): Path traversal in AVideo (critical 9.9)
- [CVE-2022-32572](https://insights.sbomify.com/CVE-2022-32572/): Command injection in AVideo (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33238 is a medium-severity path traversal vulnerability in Wwbn Avideo, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33238 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions; fixed in 26.0
- wwbn/avideo (Packagist): affected all versions; fixed in 26.0

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-33238/ (Markdown: https://insights.sbomify.com/CVE-2026-33238/index.md)
```

## Sources

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

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