Skip to main content
VulnerabilityPublished Updated

CVE-2025-25214: WWBN AVideo · Race Condition

Affects WWBN AVideoSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WWBN AVideoAffected
  • =14.4
Fixed in–

AI-suggested

  1. Immediately restrict access to the aVideoEncoder.json.php endpoint, especially the unzip functionality, by implementing network-level controls such as IP whitelisting or VPN-only access.
  2. Apply strict input validation and sanitization on all HTTP requests targeting the unzip functionality to prevent malformed or malicious payloads.
  3. Implement application-level concurrency controls, such as mutexes or locks, to ensure proper synchronization when accessing shared resources during unzip operations.
  4. Monitor web server and application logs for unusual patterns of HTTP requests targeting the vulnerable endpoint, including rapid or repeated unzip requests.
  5. If possible, isolate the AVideo server in a segmented network zone with limited access to critical infrastructure.
  6. Engage with WWBN for official patches or updates and plan for rapid deployment once available.
  7. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block exploit attempts targeting this vulnerability.
  8. Conduct regular security assessments and penetration testing focused on concurrency and race condition vulnerabilities in the application.

Description

A race condition vulnerability exists in the aVideoEncoder.json.php unzip functionality of WWBN AVideo 14.4 and dev master commit 8a8954ff. A series of specially crafted HTTP request can lead to arbitrary code execution.

References

Community reviews

Loading reviews…