# CVE-2026-33513: AVideo has an Unauthenticated Local File Inclusion in API locale (RCE possible with writable PHP)

> Unauthenticated attackers can exploit path traversal in the locale API to include arbitrary PHP files, leading to information disclosure and potential remote code execution.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-8fw8-q79c-fp9m

## What is CVE-2026-33513?

CVE-2026-33513 is a high-severity path traversal vulnerability in Wwbn Avideo, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. In versions up to and including 26.0, an unauthenticated API endpoint (`APIName=locale`) concatenates user input into an `include` path with no canonicalization or whitelist. Path traversal is accepted, so arbitrary PHP files under the web root can be included. In our test this yielded confirmed file disclosure and code execution of existing PHP content (e.g., `view/about.php`), and it *can* escalate to RCE if an attacker can place or control a PHP file elsewhere in the tree. As of time of publication, no patched versions are available.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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-33513?

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

## Is CVE-2026-33513 being exploited?

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

What it is: CVE-2026-33513 is a high-severity path traversal vulnerability in Wwbn Avideo, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33513 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-33513/ (Markdown: https://insights.sbomify.com/CVE-2026-33513/index.md)
```

## Sources

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

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