# CVE-2021-26795: SQL injection in n/a

> Attackers can exploit SQL injection in the Roster Management feature to obtain sensitive information from the TalariaX sendQuick Alert Plus Server Admin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mhfj-r7pj-492h

## What is CVE-2021-26795?

CVE-2021-26795 is a high-severity SQL injection vulnerability in n/a, published on 14 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL Injection vulnerability in /appliance/shiftmgn.php in TalariaX sendQuick Alert Plus Server Admin 4.3 before 8HF11 allows attackers to obtain sensitive information via a Roster Time to Roster Management.

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

## Which versions are affected by CVE-2021-26795?

It affects 1 product.


Products: Talariax Sendquick Alert Plus Server Admin.

## How do I fix CVE-2021-26795?

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

## Is CVE-2021-26795 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26795 and fix it if it is affected.

What it is: CVE-2021-26795 is a high-severity SQL injection vulnerability in n/a, published on 14 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26795 in the wild and no public exploit code.

Affected product: n/a. 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-2021-26795/ (Markdown: https://insights.sbomify.com/CVE-2021-26795/index.md)
```

## Sources

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

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