VulnerabilityPublished 23 Mar 2026

CVE-2026-33723: WWBN AVideo · SQL Injection

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.1High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: 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 on 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 installations to versions beyond 26.0 where the patch commit 36dfae22059fbd66fd34bbc5568a838fc0efd66c has been applied. If upgrading is not immediately possible, implement strict input validation and sanitization on the user_id parameter at the web application firewall (WAF) or application layer to block malicious SQL payloads. Employ parameterized queries or prepared statements in custom code if modifications are made. Restrict authenticated user privileges to the minimum necessary to reduce the risk of exploitation by compromised accounts. Monitor logs for unusual database queries or unexpected access patterns related to subscription functionality. Conduct regular security audits and penetration tests focusing on injection flaws. Additionally, enforce multi-factor authentication (MFA) to reduce the risk of account compromise that could lead to exploitation of this vulnerability.

Description

CVE-2026-33723 is a high-severity SQL Injection vulnerability in WWBN AVideo versions up to 26.0. The flaw exists in the Subscribe::save() method where user input from $_POST['user_id'] is concatenated directly into an SQL INSERT statement without sanitization or parameterization. An authenticated attacker can exploit this to execute arbitrary SQL commands, potentially extracting sensitive data such as password hashes, API keys, and encryption salts. The vulnerability requires authentication but no user interaction beyond sending crafted requests. A patch has been committed to fix this issue. Organizations using affected versions should update promptly to prevent data breaches. The vulnerability impacts confidentiality severely, with limited impact on integrity and no impact on availability. Countries with significant WWBN AVideo usage and strategic interest in video platforms are at higher risk.

Impact

The primary impact of this vulnerability is a severe breach of confidentiality, as attackers can extract sensitive data including password hashes, API keys, and encryption salts from the backend database. This can lead to account takeovers, unauthorized access to other integrated systems, and further lateral movement within the affected environment. While the integrity impact is limited to potential unauthorized data insertion or modification via SQL injection, the vulnerability does not affect system availability. Organizations relying on WWBN AVideo for video hosting or streaming services risk significant data exposure and reputational damage if exploited. The requirement for authentication limits the attack surface to users with valid credentials, but insider threats or compromised accounts can still leverage this flaw. The absence of known exploits in the wild currently reduces immediate risk, but the public disclosure and availability of a patch increase the urgency for remediation to prevent future exploitation.

Summary

CVE-2026-33723 identifies a SQL Injection vulnerability in the open-source video platform WWBN AVideo, affecting all versions up to and including 26.0. The root cause lies in the Subscribe::save() method within the objects/subscribe.php file, where the $this->users_id property is directly concatenated into an SQL INSERT query without any input sanitization or use of parameterized queries. This property is sourced from user-controlled input ($_POST['user_id']) in subscribe.json.php and subscribeNotify.json.php. Because the input is not neutralized, an authenticated attacker can inject malicious SQL code, enabling unauthorized data extraction from any database table. This includes highly sensitive information such as password hashes, API keys, and encryption salts, which could facilitate further compromise. The vulnerability is exploitable remotely over the network with low attack complexity, requiring only authenticated access and no additional user interaction. The scope is limited to installations running vulnerable versions of AVideo. A patch has been committed (commit 36dfae22059fbd66fd34bbc5568a838fc0efd66c) that addresses the issue by implementing proper input validation and parameterized queries. The CVSS v3.1 base score is 7.1, reflecting high severity due to the potential confidentiality impact and ease of exploitation with authentication.

CWE-89Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (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:37 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats