CVE-2026-35449: WWBN AVideo · Information Exposure
Affects WWBN AVideoSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% 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:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WWBNAVideo | Affected
| Fixed in– |
GitHubwwbn/AVideopkg:github/wwbn/AVideoOther threats | Affected
| 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 available, users should consider restricting access to the install/test.php script, for example by removing or securing the script, or by implementing web server access controls to prevent unauthorized HTTP access to this diagnostic endpoint.
Description
WWBN AVideo versions 26.0 and earlier contain a vulnerability where the install/test.php diagnostic script is accessible via HTTP due to a disabled CLI-only access guard. This exposure allows unauthenticated users to view sensitive information such as video viewer IP addresses, session IDs, and user agents. The vulnerability is classified as CWE-200, indicating exposure of sensitive information to unauthorized actors. The CVSS score is 5.3, reflecting a medium severity impact primarily on confidentiality. No official patch or remediation guidance is currently documented by the vendor. There are no known exploits in the wild at this time.