# WWBN AVideo has an Incomplete fix: Directory traversal bypass via query string in ReceiveImage downloadURL parameters

Advisory record · `GHSA-m63r-m9jh-3vc6`

- **Identifiers:** `GHSA-m63r-m9jh-3vc6` · `CVE-2026-41062` · `PKSA-pt2z-fxr4-fvmc`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 14 Apr 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Apr 2026, 23:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wwbn/avideo` (Packagist): affected `<=29.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GHSA-m63r-m9jh-3vc6 affects wwbn/avideo versions up to and including 29.0, with no fixed version listed. An authenticated user with upload permission can send a crafted URL in the ReceiveImage download parameters, so that a traversal sequence in the query string bypasses the existing path check and reads arbitrary server files. Image-format files can be retrieved via the video thumbnail URL, and other file existence and size is leaked. No fix is listed; the source gives a suggested code change, but no released version or workaround is named.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0072, the 54th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m63r-m9jh-3vc6)

## Sources

- [GitHub Advisory Database: GHSA-m63r-m9jh-3vc6](https://github.com/advisories/GHSA-m63r-m9jh-3vc6)
- [OSV: GHSA-m63r-m9jh-3vc6](https://osv.dev/vulnerability/GHSA-m63r-m9jh-3vc6)
- <https://github.com/WWBN/AVideo/security/advisories/GHSA-f4f9-627c-jh33>
- <https://github.com/WWBN/AVideo/security/advisories/GHSA-m63r-m9jh-3vc6>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41062>
- <https://github.com/WWBN/AVideo/commit/2375eb5e0a6d3cbcfb05377657d0820a7d470b1d>
- <https://github.com/WWBN/AVideo/commit/bd11c16ec894698e54e2cdae25026c61ad1ed441>
- <https://github.com/WWBN/AVideo>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m63r-m9jh-3vc6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m63r-m9jh-3vc6/>. Everything for agents: <https://agentprime.io/llms.txt>.
