EUVD-2026-103010
GHSA-hcjf-66qr-8j38
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege API user
-
ExploitCraft malicious order_by/group_by parameter
-
ExecutionBypass SqlGuard denylist via EXTRACTVALUE/UPDATEXML
-
ImpactExfiltrate other users' rows and tables
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 an authenticated low-privilege account (PR:L) able to reach the /api/data/invoke endpoint; the attacker injects SQL through the order_by and/or group_by request fields using subqueries or the MySQL error-based functions EXTRACTVALUE/UPDATEXML, which the SqlGuard denylist fails to block. Affects AipexBase through commit 690adb9. Limiting factors: valid authentication is needed (not remote-unauthenticated), the deployment must use a backend whose SQL dialect supports the error-based functions (MySQL-style), and impact is confined to reading data - no write/modification path is described. |
| Impact | Signals are moderate and internally consistent rather than alarming. The input CVSS 4.0 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw that nonetheless REQUIRES an authenticated low-privilege account (PR:L), with confidentiality-only impact (VC:H, VI:N, VA:N) - this is a data-disclosure and row-level-security-bypass bug, not RCE or data destruction. Exploitation status: no CISA KEV listing and no EPSS score were provided, so there is no evidence of active or widespread exploitation; however, a detailed public technical writeup (hackmd) plus source-line references and a VulnCheck advisory mean exploitation methodology is publicly documented. These signals do not conflict, but the EPSS score is MISSING, so probabilistic exploitation likelihood cannot be quantified. Net assessment: a genuine but not top-tier priority - the authentication requirement and read-only impact pull real-world risk below what a 7.1 'High' label implies, and the obscure product footprint further limits mass-exploitation appeal. This warrants prompt patching for any organization actually running AipexBase, but is not a general-population emergency. |
| Exploit ScenarioDerived | An attacker who already holds a valid low-privilege AipexBase account sends a request to /api/data/invoke with a crafted order_by or group_by value containing error-based SQL (EXTRACTVALUE/UPDATEXML or a subquery). Because the SqlGuard denylist and row-level security fail to sanitize these fields, the payload executes and returns data belonging to other tenants and tables. A public technical writeup documenting the exact injection points and functions exists, lowering the skill barrier to reproduce the attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
SQL injection in AipexBase through commit 690adb9 allows an authenticated low-privilege attacker to read other users' database rows and tables by injecting SQL through the order_by and group_by fields of the /api/data/invoke endpoint. The attacker can supply subqueries or MySQL error-based functions (EXTRACTVALUE/UPDATEXML) to bypass the SqlGuard denylist and row-level security, but impact is limited to confidentiality with no write or modification path described. No public exploit identified at time of analysis; CVSS 7.1 with PR:L indicates a moderate-severity issue requiring valid authentication and a MySQL-style backend.
RemediationAI
No vendor-released patch identified at time of analysis. Until an official fix is available, implement the following compensating controls: replace the denylist-based SqlGuard with strict input validation that enforces an allowlist of permitted column names and sort directions for the order_by and group_by parameters, rejecting any input containing parentheses, subqueries, or SQL keywords; refactor OrderByBuilder and GroupByBuilder to use parameterized queries or a safe query builder that maps user input to known columns rather than concatenating strings. Apply least-privilege principles to the database account used by AipexBase so that even if injection succeeds, the attacker cannot read unintended tables, though note that row-level security bypass means this alone is insufficient. Restrict access to the /api/data/invoke endpoint to trusted users where possible, but because PR:L indicates low-privilege authenticated accounts can exploit, this only reduces the attack surface. Monitor database logs for anomalous queries containing EXTRACTVALUE, UPDATEXML, or unexpected subqueries in ORDER BY/GROUP BY clauses; consider WAF rules to block SQL injection patterns, accepting potential false positives and evasion risks. Disable verbose SQL error messages returned to clients to hinder error-based injection, though subquery-based attacks may still succeed. Check the upstream repository (https://github.com/kuafuai/aipexbase) for a fix commit and apply the patched version once released; consult the VulnCheck advisory at https://www.vulncheck.com/advisories/aipexbase-through-commit-690adb9-sql-injection-via-api-data-invoke for updates.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a CWE-89 SQL injection arising from unsafe construction of dynamic SQL ORDER BY and GROUP BY clauses. AipexBase's OrderByBuilder and GroupByBuilder classes (referenced at the vulnerable commit) concatenate user-supplied order_by and group_by parameters directly into SQL statements without parameterization or a robust allowlist. The application attempts to block attacks with a denylist-based SqlGuard, but denylists are inherently incomplete: attackers bypass it using subqueries or MySQL error-based functions such as EXTRACTVALUE and UPDATEXML, which are not on the denylist. Because these injected expressions execute within the database query, they also defeat row-level security mechanisms that normally restrict a user to their own rows, allowing an authenticated low-privilege user to read arbitrary tables and other users' data. The CPE cpe:2.3:a:kuafuai:aipexbase:*:*:*:*:*:*:*:* indicates all versions up to and including commit 690adb9 are affected; exploitation requires a backend whose SQL dialect supports the error-based functions (MySQL-style).
Know when Aipexbase 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network API reachable at AC:L but needs a valid low-privilege account so PR:L; injection reads cross-tenant data (C:H) with no documented write or availability impact (I:N/A:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
AipexBase through commit 690adb9 contains a sql injection vulnerability that allows attackers to inject SQL through the order_by and group_by fields of the /api/data/invoke endpoint. Attackers can supply subqueries or EXTRACTVALUE and UPDATEXML functions that bypass the SqlGuard denylist and row-level security, reading other users' rows and tables.
Executive ViewAI
AipexBase through commit 690adb9 contains an authenticated SQL injection flaw that could let a low-privilege user read database rows and tables belonging to other users. This creates a data confidentiality and compliance risk for organizations using the affected AipexBase build, because a valid but untrusted account could exfiltrate sensitive records. No public exploit identified at time of analysis, but leadership should prioritize containment and monitoring until a vendor fix is available.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting access to /api/data/invoke, disabling or sanitizing order_by/group_by inputs, deploying WAF and database activity monitoring, enforcing least privilege, rotating credentials, and reviewing logs for EXTRACTVALUE/UPDATEXML or subquery injection attempts.
Threat Intelligence Overview
NVD
CVE.org
Vulnrichment
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.
Exploit-DB