VulnerabilityPublished 23 Mar 2026

CVE-2026-33688: WWBN AVideo · Observable Response Discrepancy

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% 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:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Mar 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WWBNAVideo	Affected <=26.0	Fixed in–
GitHubwwbn/AVideo`pkg:github/wwbn/AVideo`Other threats	Affected <=26.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

To mitigate this vulnerability, organizations should immediately apply the official patch referenced by commit e42f54123b460fd1b2ee01f2ce3d4a386e88d157 once available. In the absence of a patch, administrators can implement the following measures: 1) Modify the password recovery endpoint to perform captcha validation before any user existence or account status checks, preventing automated enumeration. 2) Normalize all error responses to be identical regardless of username validity or account status, eliminating observable discrepancies. 3) Implement rate limiting and IP throttling on password recovery requests to reduce the feasibility of large-scale enumeration. 4) Monitor logs for suspicious enumeration patterns and block offending IP addresses. 5) Educate users about phishing risks and encourage strong, unique passwords combined with multi-factor authentication to reduce the impact of credential stuffing. 6) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block enumeration attempts targeting this endpoint. These steps collectively reduce the attack surface and limit the information leakage that facilitates further attacks.

Description

CVE-2026-33688 is a medium severity vulnerability in WWBN AVideo versions up to 26.0 that allows unauthenticated attackers to enumerate valid usernames and account statuses via the password recovery endpoint. The flaw arises because the endpoint performs user existence and account status checks before captcha validation, returning distinct JSON error messages for valid, inactive, or banned accounts. This observable response discrepancy enables attackers to harvest user information at scale without solving captchas. While no known exploits are reported in the wild, this information disclosure can facilitate targeted attacks such as phishing or brute force. A patch addressing this issue has been committed but not linked here. Organizations using affected versions should apply the patch promptly and consider additional mitigations to limit user enumeration risks.

Impact

The primary impact of this vulnerability is information disclosure through user enumeration and account status detection. Attackers can compile lists of valid usernames and identify which accounts are active, inactive, or banned. This information can be exploited to craft targeted phishing campaigns, perform credential stuffing attacks with higher success rates, or identify privileged or sensitive accounts for further compromise attempts. While the vulnerability does not directly allow account takeover or system compromise, it significantly lowers the attacker's effort in reconnaissance and increases the likelihood of successful downstream attacks. Organizations relying on WWBN AVideo for video hosting or streaming services may face increased risk of user account abuse, privacy violations, and reputational damage. The vulnerability affects all unauthenticated users, making it accessible to any external attacker scanning for vulnerable instances. No known exploits in the wild have been reported yet, but the ease of exploitation and the value of enumerated data make it a credible threat.

CWE-204Observable Response Discrepancy (opens in a new tab)
Base weakness
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
ICMP IP Total Length Field Probe (opens in a new tab)
ICMP IP 'ID' Field Error Message Probe (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Mar 2026, 20:41 UTC

WeaknessesCWE-204

Technical details

References

Community reviews

Related threats