CVE-2026-33025 AVideo-Encoder is Vulnerable to Authenticated SQL Injection via ORDER BY Clause
Authenticated attackers can inject SQL via the ORDER BY clause in AVideo, allowing unauthorized data access or modification.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-33025?
CVE-2026-33025 is a high-severity SQL injection vulnerability in WWBN AVideo-Encoder, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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 real_escape_string() 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.
Weakness: CWE-89
Which versions are affected by CVE-2026-33025?
It affects 1 product.
Products include Wwbn Avideo-Encoder.
How do I fix CVE-2026-33025?
No fix has been published for CVE-2026-33025 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-33025 being exploited?
There is no known exploitation of CVE-2026-33025 in the wild and no public exploit code.
Other vulnerabilities in WWBN AVideo-Encoder
Sources
Also known as GHSA-5qvj-5h75-27pj.