CVE-2026-45731: WWBN AVideo: Authenticated Arbitrary File Read in view/update.php
Summary view/update.php reads $POST['updateFile'] as a relative path under updatedb/ and passes it to PHP's file() for line-by-line execution as part of a database migration. An authenticated administrator can abuse this to read arbitrary text files reachable from the web-server process — especially valuable on misconfigured deployments where /etc/passwd, .env, or other sibling-app configs are reachable relative to the AVideo directory.
Details view/update.php, lines 134-145 (excerpt):
if (!empty($POST['updateFile'])) { $dir = Video::getStoragePath() . "cache"; rrmdir($dir); / …unrelated cache-clear… /
if (fileexists($logfile . "log")) { unlink($logfile . "log"); // ... } $lines = file("{$global['systemRootPath']}updatedb/{$POST['updateFile']}"); The User::isAdmin() and adminSecurityCheck(true) guards at lines 12-15 enforce admin auth, but $POST['updateFile'] is concatenated into a path without any sanitization. file() returns the file's contents as an array of lines; the script subsequently iterates them and echoes the SQL it would run.
PoC POST /view/update.php Content-Type: application/x-www-form-urlencoded
updateFile=../../../../etc/passwd Result: the script attempts to load /etc/passwd (relative to {systemRootPath}updatedb/), echoing each line in the migration-runner HTML output. $POST['updateFile'] traversal accepted, no extension guard, no in-array whitelist.
Attempting ../../../../proc/self/environ similarly reveals web-server environment variables on Linux.
Impact Verified on the current master branch of WWBN/AVideo (commit bc0340662…). Likely affected: every release where view/update.php contains the $POST['updateFile'] consumer — pattern predates 2024.
Other sources
WWBN AVideo is an open source video platform. In 29.0 and earlier, view/update.php reads $POST['updateFile'] as a relative path under updatedb/ and passes it to PHP's file() for line-by-line execution as part of a database migration. An authenticated administrator can abuse this to read arbitrary text files reachable from the web-server process.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-45731?
CVE-2026-45731 is considered a high severity vulnerability due to its potential to allow unauthorized access to sensitive files.
How do I fix CVE-2026-45731?
To fix CVE-2026-45731, ensure that user input is properly sanitized and restrict file access only to authorized directories.
Who is affected by CVE-2026-45731?
CVE-2026-45731 affects versions of the WWBN/AVideo package up to and including version 29.0.
What is the exploit method for CVE-2026-45731?
CVE-2026-45731 can be exploited by an authenticated administrator who manipulates the 'updateFile' parameter to read arbitrary files.
Can CVE-2026-45731 lead to data leakage?
Yes, CVE-2026-45731 can potentially lead to data leakage by allowing access to sensitive text files on the web server.