CVE-2026-41062: WWBN AVideo has an Incomplete fix Path Traversal Vulnerability
MODERATECVE-2026-41062 is a MODERATE (CVSS 6.5) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting WWBN AVideo has an Incomplete fix libraries in the Packagist ecosystem. The issue involves directory traversal bypass via query string in receiveimage downloadurl parameters. Remediation is available in the latest vendor maintenance releases.
CVE-2026-41062 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-41062
To remediate this vulnerability, upgrade all affected WWBN AVideo has an Incomplete fix dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade wwbn/avideo to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for wwbn/avideo
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-41062, inspect your project dependencies for WWBN AVideo has an Incomplete fix:
inspect dependencies for wwbn/avideo
Analyze the terminal output to locate any version of WWBN AVideo has an Incomplete fix in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In WWBN AVideo has an Incomplete fix, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-41062 Affected WWBN AVideo has an Incomplete fix Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
wwbn/avideo
|
Packagist |
≤ 29.0
|
|
References
Frequently Asked Questions
What is CVE-2026-41062?
Which WWBN AVideo has an Incomplete fix versions are affected?
What version fixes CVE-2026-41062?
Is wwbn/avideo affected?
What is the CVSS score of CVE-2026-41062?
What CWE is associated with CVE-2026-41062?
How can I check Packagist dependencies for CVE-2026-41062?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m63r-m9jh-3vc6",
"modified" : "2026-04-24T20:41:10Z",
"published" : "2026-04-14T23:23:14Z",
"aliases" : [ "CVE-2026-41062" ],
"summary" : "WWBN AVideo has an Incomplete fix: Directory traversal bypass via query string in ReceiveImage downloadURL parameters",
"details" : "## Summary\n\nThe directory traversal fix introduced in commit 2375eb5e0 for `objects/aVideoEncoderReceiveImage.json.php` only checks the URL **path component** (via `parse_url($url, PHP_URL_PATH)`) for `..` sequences. However, the downstream function `try_get_contents_from_local()` in `objects/functionsFile.php` uses `explode('/videos/', $url)` on the **full URL string** including the query string. An attacker can place the `/videos/../../` traversal payload in the query string to bypass the security check and read arbitrary files from the server filesystem.\n\n## Details\n\nThe security fix at commit 2375eb5e0 added a traversal check at `objects/aVideoEncoderReceiveImage.json.php:49`:\n\n```php\n$decodedPath = urldecode((string)(parse_url($_REQUEST[$value], PHP_URL_PATH) ?? ''));\nif (strpos($decodedPath, '..') !== false) {\n unset($_REQUEST[$value]);\n}\n```\n\nThis only inspects the **path component** of the URL. For a URL like `http://TARGET/x?a=/videos/../../etc/passwd`, `parse_url()` returns `/x` as the path — no `..` is found.\n\nThe URL then passes through `isValidURL()` (`objects/functions.php:4203`) which accepts it because `FILTER_VALIDATE_URL` considers `..` in query strings valid per RFC 3986.\n\nIt also passes `isSSRFSafeURL()` (`objects/functions.php:4264`) because the host matches `webSiteRootURL`, causing an early return at line 4294.\n\nThe URL reaches `url_get_contents()` (`objects/functions.php:1938`) which calls `try_get_contents_from_local()` (`objects/functionsFile.php:214`):\n\n```php\nfunction try_get_contents_from_local($url)\n{\n // ...\n $parts = explode('/videos/', $url);\n if (!empty($parts[1])) {\n // ...\n $tryFile = \"{$global['systemRootPath']}{$encoder}videos/{$parts[1]}\";\n if (file_exists($tryFile)) {\n return file_get_contents($tryFile);\n }\n }\n return false;\n}\n```\n\n`explode('/videos/', $url)` operates on the **entire URL string** including the query string. For the malicious URL, `$parts[1]` becomes `../../../../../../etc/passwd`, constructing a path like `/var/www/html/AVideo/Encoder/videos/../../../../../../etc/passwd` which PHP's filesystem functions resolve to `/etc/passwd`.\n\nThe file content is returned to the caller and written to the video's thumbnail path via `_file_put_contents()`. All four `downloadURL_*` parameters (`downloadURL_image`, `downloadURL_gifimage`, `downloadURL_webpimage`, `downloadURL_spectrumimage`) are affected.\n\n## PoC\n\nPrerequisites: An authenticated AVideo user account with upload permission and an existing video they own (with known `videos_id`).\n\n1. Identify the AVideo instance's domain (e.g., `https://avideo.example.com`).\n\n2. Send a POST request to the ReceiveImage endpoint with the traversal payload in the query string:\n\n```bash\ncurl -s -b \"PHPSESSID=<session_cookie>\" \\\n \"https://avideo.example.com/objects/aVideoEncoderReceiveImage.json.php\" \\\n -d \"videos_id=<YOUR_VIDEO_ID>\" \\\n -d \"downloadURL_image=http://avideo.example.com/x?a=/videos/../../../../../../etc/passwd\"\n```\n\n3. The response will include `jpgDestSize` indicating the file was read and written (confirming file existence and revealing file size).\n\n4. For files that pass image validation (e.g., other users' uploaded images at known paths), the content persists at the video's thumbnail URL and can be retrieved:\n\n```bash\ncurl -s \"https://avideo.example.com/videos/<videoFileName>.jpg\"\n```\n\n5. Non-image files (e.g., `/etc/passwd`, configuration files) are written but then deleted by `deleteInvalidImage()`. However, file existence and size are still leaked, and a race condition exists between the write and the deletion.\n\n## Impact\n\n- **Arbitrary file read**: An authenticated user with upload permission can read any file on the server filesystem that the web server process has access to. Files that pass image validation (PNG/JPEG/GIF) are fully exfiltrable via the video thumbnail URL.\n- **Information disclosure**: For non-image files, file existence and size are leaked through the `jpgDestSize` response field.\n- **Configuration exposure**: Server configuration files, database credentials (`videos/configuration.php`), and other sensitive data can be targeted. While PHP files would be deleted by `deleteInvalidImage`, there is a race window between write and deletion.\n- **Bypass of security fix**: This directly bypasses the path traversal mitigation added in commit 2375eb5e0.\n\n## Recommended Fix\n\nThe `..` check in `aVideoEncoderReceiveImage.json.php` should inspect the **full URL** (after URL-decoding), not just the path component. Additionally, `try_get_contents_from_local()` should validate its derived path.\n\n**Fix 1 — Check the full URL in ReceiveImage (objects/aVideoEncoderReceiveImage.json.php:49):**\n\n```php\n// Replace:\n$decodedPath = urldecode((string)(parse_url($_REQUEST[$value], PHP_URL_PATH) ?? ''));\nif (strpos($decodedPath, '..') !== false) {\n\n// With:\n$decodedFull = urldecode((string)$_REQUEST[$value]);\nif (strpos($decodedFull, '..') !== false) {\n```\n\n**Fix 2 — Add path validation in try_get_contents_from_local (objects/functionsFile.php:229):**\n\n```php\n$tryFile = \"{$global['systemRootPath']}{$encoder}videos/{$parts[1]}\";\n// Add traversal check:\n$realTryFile = realpath($tryFile);\n$videosDir = realpath(\"{$global['systemRootPath']}{$encoder}videos/\");\nif ($realTryFile === false || !str_starts_with($realTryFile, $videosDir)) {\n return false;\n}\nif (file_exists($tryFile)) {\n return file_get_contents($tryFile);\n}\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "wwbn/avideo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "29.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-f4f9-627c-jh33"
}, {
"type" : "WEB",
"url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-m63r-m9jh-3vc6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41062"
}, {
"type" : "WEB",
"url" : "https://github.com/WWBN/AVideo/commit/2375eb5e0a6d3cbcfb05377657d0820a7d470b1d"
}, {
"type" : "WEB",
"url" : "https://github.com/WWBN/AVideo/commit/bd11c16ec894698e54e2cdae25026c61ad1ed441"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/WWBN/AVideo"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-14T23:23:14Z",
"nvd_published_at" : "2026-04-21T23:16:21Z"
}
}