# CVE-2026-33493: AVideo has a Path Traversal in import.json.php Allows Private Video Theft and Arbitrary File Read/Deletion via fileURI Parameter

> Authenticated users can exploit path traversal in import.json.php to steal private videos, read arbitrary files, or delete files via the fileURI parameter.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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:** No
- **Published:** 23 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-83xq-8jxj-4rxm

## What is CVE-2026-33493?

CVE-2026-33493 is a high-severity path traversal vulnerability in Wwbn Avideo, published on 23 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. In versions up to and including 26.0, the `objects/import.json.php` endpoint accepts a user-controlled `fileURI` POST parameter with only a regex check that the value ends in `.mp4`. Unlike `objects/listFiles.json.php`, which was hardened with a `realpath()` + directory prefix check to restrict paths to the `videos/` directory, `import.json.php` performs no directory restriction. This allows an authenticated user with upload permission to: (1) steal any other user's private video files by importing them into their own account, (2) read `.txt`/`.html`/`.htm` files adjacent to any `.mp4` file on the filesystem, and (3) delete `.mp4` and adjacent text files if writable by the web server process. Commit e110ff542acdd7e3b81bdd02b8402b9f6a61ad78 contains a patch.

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

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

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 to 26.0 | None |
| `wwbn/avideo` | Packagist | All versions to 26.0 | None |

Products: Wwbn Avideo.

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

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

## Is CVE-2026-33493 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33493 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-33493 and fix it if it is affected.

What it is: CVE-2026-33493 is a high-severity path traversal vulnerability in Wwbn Avideo, published on 23 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-33493 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 26.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 26.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-33493/ (Markdown: https://insights.sbomify.com/CVE-2026-33493/index.md)
```

## Sources

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

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