Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-86189 – Unauthenticated Arbitrary File Write (Path Traversal) – WWBN AVideo ≤ 29.0

Be the first to know when new zero-days emerge:

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.php derives the file write destination from the avideoRelativePath parameter, 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 notifyCode value is non-empty, so any previously issued ciphertext (e.g., a captured video_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.php endpoint, particularly where the standAloneFFMPEG feature is enabled.
    • Deploy a WAF or reverse-proxy rule to block requests containing path traversal sequences or unexpected values in the avideoRelativePath/avideoPath parameters.
    • 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.

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(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge