Summary
CVE-2026-86189 is a critical arbitrary file write vulnerability in WWBN AVideo, caused by unsafe handling of a user-supplied path parameter in the notify.ffmpeg.json.php endpoint. The flaw allows unauthenticated attackers to write attacker-controlled files to the application root and subdirectories, and has been rated CRITICAL severity.
Technical details
- Root cause:
notify.ffmpeg.json.phpderives the file write destination from theavideoRelativePathparameter, which is not validated for path traversal or restricted to an intended directory, even though a related field (avideoPath) is format-checked. - Authentication bypass: the endpoint’s token check only verifies that a decrypted
notifyCodevalue is non-empty, so any previously issued ciphertext (e.g., a capturedvideo_id_hash) can be replayed to satisfy the check without a valid, fresh token. - Attack vector: network-reachable, no authentication or user interaction required, low attack complexity.
- Impact: unauthenticated write of arbitrary content to files under the application root and subdirectories, which can affect confidentiality, integrity, and availability of the application and, depending on what is overwritten, of the underlying host.
Affected software
- WWBN AVideo, versions 0 through 29.0
Severity
- CVSS v3.1 Base Score: 9.8 (CRITICAL)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: no official patched release is currently identified in the vulnerability record; monitor the vendor’s GitHub repository and security advisories for a fixed version and upgrade as soon as one is released.
- If no patch is available:
- Restrict or disable network access to the
notify.ffmpeg.json.phpendpoint, particularly where thestandAloneFFMPEGfeature is enabled. - Deploy a WAF or reverse-proxy rule to block requests containing path traversal sequences or unexpected values in the
avideoRelativePath/avideoPathparameters. - Restrict outbound/inbound access to the AVideo instance to trusted networks until a fix is applied.
- Monitor application directories for unexpected new or modified files.
- Restrict or disable network access to the
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Page title:
Sign In - AVideo,AVideo - Raw response body:
id="avideoModal",avideoAlert(,avideoModalIframe(

