# CVE-2026-111718: AipexBase through commit 690adb9 SQL Injection via /api/data/invoke

> Attackers can inject SQL via the /api/data/invoke endpoint to bypass security controls and read unauthorized data from other users' rows and tables.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-hcjf-66qr-8j38

## What is CVE-2026-111718?

CVE-2026-111718 is a high-severity SQL injection vulnerability in kuafuai aipexbase, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-111718?


## How do I fix CVE-2026-111718?

No fix has been published for CVE-2026-111718 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111718 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111718 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111718 and fix it if it is affected.

What it is: CVE-2026-111718 is a high-severity SQL injection vulnerability in kuafuai aipexbase, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111718 exists.

Affected product: kuafuai aipexbase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111718/ (Markdown: https://insights.sbomify.com/CVE-2026-111718/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111718
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111718
- OSV: https://osv.dev/vulnerability/CVE-2026-111718

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111718/
Summaries are generated and may contain mistakes; the official description above is the record.