CVE-2026-33651: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in WWBN AVideo
WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `remindMe.json.php` endpoint passes `$_REQUEST['live_schedule_id']` through multiple functions without sanitization until it reaches `Scheduler_commands::getAllActiveOrToRepeat()`, which directly concatenates it into a SQL `LIKE` clause. Although intermediate functions (`new Live_schedule()`, `getUsers_idOrCompany()`) apply `intval()` internally, they do so on local copies within `ObjectYPT::getFromDb()`, leaving the original tainted variable unchanged. Any authenticated user can perform time-based blind SQL injection to extract arbitrary database contents. Commit 75d45780728294ededa1e3f842f95295d3e7d144 contains a patch.
AI Analysis
Technical Summary
CVE-2026-33651 is an SQL injection vulnerability classified under CWE-89 affecting WWBN's open-source video platform, AVideo, in versions up to and including 26.0. The vulnerability exists in the remindMe.json.php endpoint, where the 'live_schedule_id' parameter from $_REQUEST is passed through multiple functions without proper sanitization. While intermediate functions such as new Live_schedule() and getUsers_idOrCompany() internally apply intval() to local copies of the parameter within ObjectYPT::getFromDb(), the original input remains unsanitized. This unsanitized input is then directly concatenated into a SQL LIKE clause within Scheduler_commands::getAllActiveOrToRepeat(), enabling an authenticated attacker to conduct time-based blind SQL injection attacks. These attacks allow extraction of arbitrary database contents by exploiting the SQL query logic. The vulnerability does not require user interaction beyond authentication and has a CVSS 3.1 base score of 8.1, indicating high severity with network attack vector, low attack complexity, and high impact on confidentiality and integrity. The availability impact is rated none. Although no known exploits are currently reported in the wild, a patch has been committed (commit 75d45780728294ededa1e3f842f95295d3e7d144) to remediate the issue by properly sanitizing inputs before SQL query construction.
Potential Impact
The primary impact of this vulnerability is unauthorized disclosure of sensitive data stored in the AVideo platform's database. Attackers with valid authentication can exploit the SQL injection flaw to extract user information, video metadata, schedules, and potentially other confidential data. This compromises confidentiality and integrity of the system's data. Since the vulnerability allows arbitrary database content extraction, it could lead to privacy violations, intellectual property theft, and further escalation of attacks if sensitive credentials or configuration data are exposed. Although availability is not directly impacted, the breach of trust and data loss can severely damage organizational reputation and user trust. Organizations relying on AVideo for video hosting and streaming services are at risk of data breaches, regulatory non-compliance, and potential legal consequences. The ease of exploitation due to low attack complexity and network accessibility increases the urgency of remediation.
Mitigation Recommendations
Organizations should immediately upgrade AVideo installations to versions beyond 26.0 where the patch has been applied. If upgrading is not immediately feasible, implement input validation and sanitization at the application level for the 'live_schedule_id' parameter, ensuring that only strictly validated integer values are accepted. Employ parameterized queries or prepared statements in all database interactions to eliminate direct concatenation of user inputs into SQL commands. Conduct a thorough code audit of all endpoints handling user input to identify and remediate similar injection risks. Restrict access to the remindMe.json.php endpoint to trusted users and monitor logs for suspicious activity indicative of SQL injection attempts. Additionally, implement database activity monitoring and anomaly detection to identify potential exploitation attempts. Regularly update and patch all components of the AVideo platform and maintain a robust incident response plan to address any detected breaches promptly.
Affected Countries
United States, Germany, France, United Kingdom, Canada, Australia, India, Brazil, Japan, South Korea
CVE-2026-33651: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in WWBN AVideo
Description
WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `remindMe.json.php` endpoint passes `$_REQUEST['live_schedule_id']` through multiple functions without sanitization until it reaches `Scheduler_commands::getAllActiveOrToRepeat()`, which directly concatenates it into a SQL `LIKE` clause. Although intermediate functions (`new Live_schedule()`, `getUsers_idOrCompany()`) apply `intval()` internally, they do so on local copies within `ObjectYPT::getFromDb()`, leaving the original tainted variable unchanged. Any authenticated user can perform time-based blind SQL injection to extract arbitrary database contents. Commit 75d45780728294ededa1e3f842f95295d3e7d144 contains a patch.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33651 is an SQL injection vulnerability classified under CWE-89 affecting WWBN's open-source video platform, AVideo, in versions up to and including 26.0. The vulnerability exists in the remindMe.json.php endpoint, where the 'live_schedule_id' parameter from $_REQUEST is passed through multiple functions without proper sanitization. While intermediate functions such as new Live_schedule() and getUsers_idOrCompany() internally apply intval() to local copies of the parameter within ObjectYPT::getFromDb(), the original input remains unsanitized. This unsanitized input is then directly concatenated into a SQL LIKE clause within Scheduler_commands::getAllActiveOrToRepeat(), enabling an authenticated attacker to conduct time-based blind SQL injection attacks. These attacks allow extraction of arbitrary database contents by exploiting the SQL query logic. The vulnerability does not require user interaction beyond authentication and has a CVSS 3.1 base score of 8.1, indicating high severity with network attack vector, low attack complexity, and high impact on confidentiality and integrity. The availability impact is rated none. Although no known exploits are currently reported in the wild, a patch has been committed (commit 75d45780728294ededa1e3f842f95295d3e7d144) to remediate the issue by properly sanitizing inputs before SQL query construction.
Potential Impact
The primary impact of this vulnerability is unauthorized disclosure of sensitive data stored in the AVideo platform's database. Attackers with valid authentication can exploit the SQL injection flaw to extract user information, video metadata, schedules, and potentially other confidential data. This compromises confidentiality and integrity of the system's data. Since the vulnerability allows arbitrary database content extraction, it could lead to privacy violations, intellectual property theft, and further escalation of attacks if sensitive credentials or configuration data are exposed. Although availability is not directly impacted, the breach of trust and data loss can severely damage organizational reputation and user trust. Organizations relying on AVideo for video hosting and streaming services are at risk of data breaches, regulatory non-compliance, and potential legal consequences. The ease of exploitation due to low attack complexity and network accessibility increases the urgency of remediation.
Mitigation Recommendations
Organizations should immediately upgrade AVideo installations to versions beyond 26.0 where the patch has been applied. If upgrading is not immediately feasible, implement input validation and sanitization at the application level for the 'live_schedule_id' parameter, ensuring that only strictly validated integer values are accepted. Employ parameterized queries or prepared statements in all database interactions to eliminate direct concatenation of user inputs into SQL commands. Conduct a thorough code audit of all endpoints handling user input to identify and remediate similar injection risks. Restrict access to the remindMe.json.php endpoint to trusted users and monitor logs for suspicious activity indicative of SQL injection attempts. Additionally, implement database activity monitoring and anomaly detection to identify potential exploitation attempts. Regularly update and patch all components of the AVideo platform and maintain a robust incident response plan to address any detected breaches promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T15:23:42.217Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c18de6f4197a8e3b82dd81
Added to database: 3/23/2026, 7:00:54 PM
Last enriched: 3/23/2026, 7:17:09 PM
Last updated: 3/24/2026, 5:18:53 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.