CVE-2026-40935: WWBN AVideo · Guessable CAPTCHA
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.2% chance of exploitation in 30 days – higher than 12% 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:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 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
A fix is available in the codebase as identified by commit bf1c76989e6a9054be4f0eb009d68f0f2464b453. Users of WWBN AVideo should apply this fix or upgrade to a version including it. No official vendor advisory or patch release is currently referenced, so users should monitor the vendor's channels for an official update. Until patched, consider implementing additional rate limiting or CAPTCHA validation improvements to mitigate brute-force attempts.
Description
WWBN AVideo versions 29.0 and earlier contain a vulnerability in the CAPTCHA implementation where the CAPTCHA length can be set by an unauthenticated client without validation, allowing generation of a 1-character CAPTCHA. Because the CAPTCHA comparison is case-insensitive over a limited alphabet and failed attempts do not consume the session token, an attacker can brute-force the CAPTCHA in about 33 attempts per session. This affects any endpoint relying on Captcha::validation(), such as user registration and password recovery. A fix is available in commit bf1c76989e6a9054be4f0eb009d68f0f2464b453, but no official vendor advisory or patch release is referenced.