# CVE-2026-46337: WWBN AVideo: Unauthenticated Arbitrary Image Read via Path Traversal in `view/img/image404Raw.php`

> Unauthenticated attackers can read arbitrary image files on the server via path traversal in AVideo, exposing private user data and admin assets.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-w4qq-74h6-58wq

## What is CVE-2026-46337?

CVE-2026-46337 is a medium-severity path traversal vulnerability in Wwbn Avideo, published on 29 May 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 29.0 and earlier, an unauthenticated remote attacker can read arbitrary image files anywhere on disk that the PHP user can open — including private user-profile photos that the application's normal serving wrappers gate behind ACLs, admin-uploaded thumbnails, encrypted-video poster frames, and image content under sibling-app directories reachable via .. traversal. The endpoint requires no authentication.

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

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

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 29.0 | None |
| `WWBN/AVideo` | Packagist | All versions to 29.0 | None |

Products: Wwbn Avideo.

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

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

## Is CVE-2026-46337 being exploited?

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

What it is: CVE-2026-46337 is a medium-severity path traversal vulnerability in Wwbn Avideo, published on 29 May 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-46337 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-46337/ (Markdown: https://insights.sbomify.com/CVE-2026-46337/index.md)
```

## Sources

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

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