VulnerabilityPublished 22 Mar 2026

CVE-2026-33296: WWBN AVideo · Open Redirect

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.1 Low : upgrade to 26.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

2.1Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: Active
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system 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 Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 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 30 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

Upgrade AVideo and wwbn/AVideo to 26.0.

Affected software

Product	Affected	Fixed in
WWBNAVideo	Affected <26.0	Fixed in 26.0
GitHubwwbn/AVideo`pkg:github/wwbn/AVideo`Other threats	Affected <26.0	Fixed in 26.0

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

AI-suggested

Organizations should upgrade WWBN AVideo to version 26.0 or later, where the vulnerability is fixed by proper validation and encoding of the redirectUri parameter. Until upgrade is possible, administrators can implement input validation on the redirectUri parameter at the web server or application firewall level to allow only trusted domains or relative paths. Employing Content Security Policy (CSP) headers can help reduce the risk of malicious script execution following redirection. User education on recognizing phishing attempts and verifying URLs before entering credentials is critical. Monitoring logs for unusual redirectUri parameter values may help detect exploitation attempts. Additionally, consider implementing multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing attacks leveraging this vulnerability.

Description

CVE-2026-33296 is an open redirect vulnerability in WWBN AVideo versions prior to 26.0. The flaw occurs in the login flow where a user-supplied redirectUri parameter is directly assigned to JavaScript's document.location without proper encoding. This allows an attacker to redirect users to malicious sites after login completion. Exploitation requires user interaction and no authentication is needed. The vulnerability has a low CVSS score of 2.1 and no known exploits in the wild. Version 26.0 of AVideo addresses this issue by properly validating or encoding the redirectUri parameter.

Impact

The primary impact of this vulnerability is the facilitation of phishing and social engineering attacks. Attackers can exploit the open redirect to send users to malicious websites that may mimic the legitimate platform or deliver malware payloads. While the vulnerability does not directly compromise system confidentiality, integrity, or availability, it undermines user trust and can lead to credential theft or session hijacking if users are tricked into entering sensitive information on attacker-controlled sites. Organizations deploying WWBN AVideo in environments with sensitive user data or high-value targets may face reputational damage and increased risk of downstream attacks. The low CVSS score reflects the limited direct technical impact but does not diminish the potential for indirect harm through user deception. Since exploitation requires user interaction, the threat is mitigated somewhat by user awareness but remains a concern for phishing-prone environments.

CWE-601URL Redirection to Untrusted Site (Open Redirect) (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (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 29 Mar 2026, 20:12 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats