VulnerabilityPublished 23 Mar 2026

CVE-2026-33488: WWBN AVideo · Inadequate Encryption Strength

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.4 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.4High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 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

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

Organizations should immediately upgrade WWBN AVideo to a version that includes the patch addressing CVE-2026-33488 or apply the patch from commit 00d979d87f8182095c8150609153a43f834e351e if available. The RSA key size used in the PGP 2FA system must be increased to at least 2048 bits to ensure cryptographic strength against factoring attacks. Additionally, authentication checks must be enforced on the `generateKeys.json.php` and `encryptMessage.json.php` endpoints to prevent anonymous users from abusing CPU-intensive operations. Monitoring and rate-limiting requests to these endpoints can further mitigate denial-of-service risks. Organizations should audit their user accounts for suspicious activity indicative of 2FA bypass attempts and consider resetting keys or forcing 2FA re-enrollment post-patch. Implementing network-level protections such as web application firewalls (WAFs) to detect anomalous traffic patterns targeting these endpoints can provide additional defense. Finally, educating users about the importance of strong 2FA methods and timely software updates is essential to reduce exposure.

Description

CVE-2026-33488 is a high-severity vulnerability in WWBN AVideo versions up to 26.0, where the LoginControl plugin's PGP 2FA system uses weak 512-bit RSA keys. These keys can be factored on commodity hardware within hours, allowing attackers to derive private keys and bypass the second authentication factor by decrypting PGP challenges. Additionally, two endpoints related to key generation and encryption lack authentication, exposing the system to resource exhaustion attacks by anonymous users. Although no exploits are currently known in the wild, the vulnerability poses a significant risk to confidentiality and integrity of user authentication. A patch has been committed to address the issue. Organizations using affected versions should urgently upgrade and restrict access to vulnerable endpoints to mitigate exploitation risks.

Impact

The primary impact of this vulnerability is the compromise of the two-factor authentication mechanism, allowing attackers to bypass the second factor and gain unauthorized access to user accounts. This undermines the confidentiality and integrity of user sessions and potentially sensitive video content or administrative controls within the AVideo platform. The unauthenticated access to CPU-intensive endpoints also exposes the platform to denial-of-service attacks, which could degrade service availability. Organizations relying on AVideo for video hosting or streaming may face account takeovers, unauthorized content access, and service disruptions. This could lead to data breaches, loss of user trust, and operational downtime. Given the ease of factoring 512-bit RSA keys with modern commodity hardware, the vulnerability is exploitable without advanced resources, increasing the risk of exploitation. While no known exploits are reported in the wild yet, the public availability of the weakness and patch details may prompt attackers to develop exploits rapidly.

CWE-326Inadequate Encryption Strength (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
Architecture and Design
Use an encryption scheme that is currently considered to be strong by experts in the field.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.3 (opens in a new tab)
V6.2.7 (opens in a new tab)
V6.2.4 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Brute Force (opens in a new tab)
Protocol Analysis (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:35 UTC

WeaknessesCWE-326

Technical details

References

Community reviews

Related threats