Quick answers
- Is CVE-2026-45731 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45731 being exploited in the wild.
- How severe is CVE-2026-45731?
- Medium severity, with a CVSS score of 3.1, published 29 May 2026.
- Which products and versions are affected?
- wwbn/avideo (Packagist) <= 29.0, ECOSYSTEM:introduced=0,last_affected=29.0; WWBN AVideo <= 29.0, 29.0 and earlier.
- Is there a fix for CVE-2026-45731?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45731 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45731?
- Check whether you run wwbn/avideo (Packagist) or WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in `view/update.php` due to insufficient sanitization of the `updateFile` POST parameter. The application concatenates this user-supplied input into a file path used by PHP's `file()` function during database migrations. An authenticated attacker with administrative privileges can use directory traversal sequences (e.g., `../../`) to bypass the intended `updatedb/` directory and read any text file reachable by the web server process, such as `/etc/passwd` or `.env` files. The vulnerability was verified on the master branch (commit bc03406) and affects versions up to and including 29.0.
Affected products
- WWBN AVideo 29.0 and earlier
Identifiers
- CVE-2026-45731
- GHSA-3mjv-375j-6h92
Timeline
- 2026-05-12: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: NVD publication date