# CVE-2026-2663: Alixhan xh-admin-backend Database Query query sql injection

> Remote attackers can exploit SQL injection in the role query API to read or modify database contents in Alixhan xh-admin-backend.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 18 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-rwf8-6fj2-4vrx

## What is CVE-2026-2663?

CVE-2026-2663 is a medium-severity SQL injection vulnerability in Alixhan xh-admin-backend, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in Alixhan xh-admin-backend up to 1.7.0. This issue affects some unknown processing of the file /frontend-api/system-service/api/system/role/query of the component Database Query Handler. Such manipulation of the argument prop leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-2663 being exploited?

There is no known exploitation of CVE-2026-2663 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2663 is a medium-severity SQL injection vulnerability in Alixhan xh-admin-backend, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2663 in the wild and no public exploit code.

Affected product: Alixhan xh-admin-backend. 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-2663/ (Markdown: https://insights.sbomify.com/CVE-2026-2663/index.md)
```

## Sources

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

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