Quick answers
- Is CVE-2026-116800 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116800 being exploited in the wild.
- How severe is CVE-2026-116800?
- Medium severity, with a CVSS score of 6.2, published 27 October 2026.
- Which products and versions are affected?
- WWBN AVideo before 29.5.0.
- Is there a fix for CVE-2026-116800?
- Yes: fixed in AVideo 29.5.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116800 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116800?
- Check whether you run 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.
How to fix
- Fixed in: AVideo 29.5.0
Technical details
The vulnerability exists in the setLanguage() function, which uses a single-pass str_replace() to remove '../' sequences from user-supplied language codes, allowing attackers to bypass this via overlapping traversal patterns like '....//'. An unauthenticated attacker can craft a malicious Accept-Language header to include PHP files outside the intended locale directory, executing arbitrary server-side code. Version 29.5.0 fixes this by implementing proper language code validation instead of simple string replacement.
Affected products
- WWBN AVideo before 29.5.0
Timeline
- 2026-10-27: disclosed
- 2026-10-19: patched