# CVE-2022-28132: SQL injection in n/a

> Authenticated attackers can exploit SQL injection in T-Soft E-Commerce 4 to access and manipulate the database, leading to data exposure and modification.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-q2xc-6c48-r5px

## What is CVE-2022-28132?

CVE-2022-28132 is a high-severity SQL injection vulnerability in n/a, published on 14 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The T-Soft E-Commerce 4 web application is susceptible to SQL injection (SQLi) attacks when authenticated as an admin or privileged user. This vulnerability allows attackers to access and manipulate the database through crafted requests. By exploiting this flaw, attackers can bypass authentication mechanisms, view sensitive information stored in the database, and potentially exfiltrate data.

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

## Which versions are affected by CVE-2022-28132?


## How do I fix CVE-2022-28132?

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

## Is CVE-2022-28132 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28132 and fix it if it is affected.

What it is: CVE-2022-28132 is a high-severity SQL injection vulnerability in n/a, published on 14 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28132 exists.

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-2022-28132/ (Markdown: https://insights.sbomify.com/CVE-2022-28132/index.md)
```

## Sources

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

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