Skip to main content
VulnerabilityPublished

CVE-2026-43874: WWBN AVideo · Code Injection

Affects WWBN AVideoSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 7.2 High.

Data as of 15 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
WWBNAVideoAffected
  • <=29.0
Fixed in–
GitHubwwbn/AVideopkg:github/wwbn/AVideoOther threatsAffected
  • <=29.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is confirmed, restrict access to WebSocket tokens and monitor for unusual WebSocket activity. Avoid using affected versions (<= 29.0) in production environments where possible.

Description

CVE-2026-43874 is a high-severity code injection vulnerability in WWBN AVideo versions up to and including 29.0. The issue arises because the server-side mitigation for a previous vulnerability (CVE-2026-40911) only strips malicious payloads in a specific JSON field ($json['msg']), but the relay function uses a different field ($msg['json']) to select outbound messages. An unauthenticated attacker can obtain a WebSocket token, connect to the WebSocket server, and send a specially crafted message that bypasses the stripping mechanism. This message is then relayed verbatim to logged-in users and executed via eval() on the client side, enabling code injection. There is a commit referenced that contains an updated fix, but no official patch or vendor advisory is provided in the data.

References

Community reviews

Loading reviews…