Attack Chain

1. An attacker authenticates to the AVideo platform with valid credentials.
2. The attacker crafts a malicious HTTP request targeting the remindMe.json.php endpoint.
3. The attacker injects SQL code into the live_schedule_id parameter within the request. This parameter is passed unsanitized to the vulnerable function.
4. The remindMe.json.php script processes the request, passing the tainted live_schedule_id to Scheduler_commands::getAllActiveOrToRepeat().
5. Scheduler_commands::getAllActiveOrToRepeat() concatenates the injected SQL code into a LIKE clause within a SQL query.
6. The application executes the malicious SQL query against the AVideo database.
7. The attacker uses time-based techniques to infer the results of the injected SQL query, extracting data bit by bit.
8. The attacker successfully exfiltrates sensitive information from the database, such as user credentials, configuration settings, or other confidential data.

Impact

Successful exploitation of CVE-2026-33651 allows any authenticated user to perform time-based blind SQL injection attacks, leading to the complete compromise of the AVideo database. This can result in the exfiltration of sensitive data, including user credentials and system configurations. Given that AVideo is a video platform, the exposed data could also include information about video content, user activity, and potentially even the videos themselves. The number of affected installations is unknown.

Recommendation

• Apply the patch from commit 75d45780728294ededa1e3f842f95295d3e7d144 to remediate CVE-2026-33651.
• Deploy the Sigma rule "Detect AVideo SQL Injection Attempt" to detect exploitation attempts against the remindMe.json.php endpoint.
• Monitor web server logs for suspicious requests containing SQL syntax in the live_schedule_id parameter of the remindMe.json.php endpoint.
• Implement input validation and sanitization for all user-supplied input to prevent SQL injection vulnerabilities.