Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as valid AVideo user
-
DeliveryCraft malicious POST request with SQL in sort parameter
-
ExploitInject SQL via ORDER BY clause
-
ExecutionExecute arbitrary SQL queries
-
ImpactExfiltrate or modify database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires authenticated user account on AVideo versions prior to 8.0. Attacker sends POST request with malicious sort[] array keys in getSqlFromPost() method to inject SQL into ORDER BY clause. No victim interaction needed. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N) indicates this is a network-exploitable vulnerability with low attack complexity requiring only low-privilege authentication, resulting in high confidentiality and integrity impacts to the vulnerable system. The requirement for authentication (PR:L) reduces the attack surface compared to unauthenticated vulnerabilities, but the low complexity means exploitation is straightforward once access is obtained. The vulnerability is limited to components like queue.json.php and index.php that process sort parameters, which may not be universally exposed in all deployments. While the 8.6 CVSS score suggests high severity, the lack of EPSS data, absence from CISA KEV, and the authentication requirement indicate this is not currently being actively exploited at scale. Organizations running AVideo-Encoder should prioritize patching based on whether they have untrusted authenticated users and whether the affected queue functionality is exposed, making this a medium-to-high priority depending on deployment context rather than an emergency patch. |
| Exploit ScenarioDerived | An authenticated attacker with low-privilege credentials logs into an AVideo-Encoder instance and navigates to the queue management interface. The attacker crafts a malicious POST request to queue.json.php containing a specially crafted sort parameter with SQL injection payloads in the array keys, such as sort[malicious_column`;DROP TABLE users;--]=asc. Because the application uses these keys directly as SQL identifiers in an ORDER BY clause without proper validation, the injected SQL commands execute against the database, allowing the attacker to extract sensitive data like user credentials, modify video metadata, or manipulate the application's data integrity with high confidence of success given the low attack complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 20, 2026
Unauthenticated SQL injection in AVideo versions before 8.0 allows authenticated attackers to manipulate database queries through unsanitized sort parameters in POST requests, potentially leading to unauthorized data access or modification. The vulnerability stems from improper use of real_escape_string() on SQL identifiers rather than string literals, rendering the escaping mechanism ineffective. Affected organizations should upgrade to version 8.0 or implement WAF rules restricting sort parameter characters to alphanumeric and underscore values.
Earlier versions of this analysis (1)
A SQL Injection vulnerability exists in AVideo, a video-sharing platform, where the getSqlFromPost() method in Object.php fails to properly sanitize $_POST['sort'] array keys used as SQL column identifiers in ORDER BY clauses. AVideo-Encoder versions prior to 8.0 are affected, allowing authenticated attackers with low privileges to execute arbitrary SQL commands and potentially extract or manipulate database contents. The CVSS score of 8.6 indicates high severity with network-based attack vector and low complexity, though no KEV listing or EPSS data suggests active exploitation has not been widely observed.
RemediationAI
Upgrade AVideo-Encoder to version 8.0 or later, which contains the fix as documented in the GitHub commit at https://github.com/WWBN/AVideo-Encoder/commit/d1c8a17ac88b5e27da9dfb7a230bbaf54aa53124 and detailed in the security advisory at https://github.com/WWBN/AVideo-Encoder/security/advisories/GHSA-5qvj-5h75-27pj. For environments where immediate upgrading is not feasible, implement a Web Application Firewall (WAF) rule to block POST requests where any sort parameter key contains characters outside the range [A-Za-z0-9_], effectively restricting sort keys to valid SQL identifier characters. As an additional mitigation layer, restrict access to the vulnerable endpoints (queue.json.php and index.php) to trusted IP ranges using network-level access controls or reverse proxy rules, reducing the attack surface to only trusted authenticated users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability affects AVideo-Encoder (CPE data indicates cpe:2.3:a:avideo:avideo-encoder versions below 8.0), a PHP-based video encoding and sharing platform. The root cause is CWE-89 (SQL Injection) where the application incorrectly relies on real_escape_string() to sanitize SQL identifiers in an ORDER BY clause. The real_escape_string() function only escapes string-context characters like quotes and null bytes, but provides no protection when user input is used directly as column names or SQL identifiers outside of quoted strings. The vulnerable code path is in the Object.php file's getSqlFromPost() method, which processes the sort parameter from POST requests and constructs dynamic SQL queries. This represents a fundamental misunderstanding of SQL injection prevention, where identifier context requires allowlisting or proper quoting mechanisms rather than string escaping.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
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.
Executive ViewAI
AVideo versions before 8.0 contain a SQL injection vulnerability in sort parameter handling that allows authenticated users to manipulate database queries and access or modify sensitive data. Organizations running AVideo must upgrade immediately to version 8.0, as this vulnerability directly threatens data confidentiality and integrity for any system handling customer or operational data through AVideo.
Vendor-released patch: AVideo version 8.0. Interim mitigation if upgrade is delayed: Deploy WAF rule to restrict sort parameters to alphanumeric characters and underscores only, and limit database user permissions to minimum required privileges.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Related Vulnerabilities in AVideo Server-Side and SQL Injection
View all 2In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-13559
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB