CVE-2026-33025: AVideo-Encoder is Vulnerable to Authenticated SQL Injection via ORDER BY Clause
AVideo is a video-sharing Platform. Versions prior to 8.0 contain a SQL Injection vulnerability in the getSqlFromPost() method of Object.php. The $POST['sort'] array keys are used directly as SQL column identifiers inside an ORDER BY clause. Although realescapestring() was applied, it only escapes string-context characters (quotes, null bytes) and provides no protection for SQL identifiers — making it entirely ineffective here. This issue has been fixed in version 8.0. To workaround this issue without upgrading, operators can apply a WAF rule to block POST requests where any sort[] key contains characters outside [A-Za-z0-9]. Alternatively, restrict access to the queue view (queue.json.php, index.php) to trusted IP ranges only.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33025?
CVE-2026-33025 has been classified as a critical severity vulnerability due to its potential for unauthorized access and data compromise.
How do I fix CVE-2026-33025?
To fix CVE-2026-33025, update your AVideo or AVideo-Encoder software to version 8.0 or higher where the vulnerability has been resolved.
What type of vulnerability is CVE-2026-33025?
CVE-2026-33025 is an authenticated SQL Injection vulnerability that affects the ORDER BY clause in the AVideo platform.
What are the affected versions of CVE-2026-33025?
CVE-2026-33025 affects all versions of AVideo and AVideo-Encoder prior to version 8.0.
What impact does CVE-2026-33025 have on my system?
CVE-2026-33025 can allow an attacker with authenticated access to manipulate SQL queries, potentially leading to data loss or corruption.