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

> SQL injection in SalonERP allows attackers to extract admin password hashes, leading to account takeover.

- **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 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xhxm-v6fm-53p3

## What is CVE-2021-45406?

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

### Official description

In SalonERP 3.0.1, a SQL injection vulnerability allows an attacker to inject payload using 'sql' parameter in SQL query while generating a report. Upon successfully discovering the login admin password hash, it can be decrypted to obtain the plain-text password.

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

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

It affects 1 product.


Products: Salonerp Project Salonerp.

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

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

## Is CVE-2021-45406 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-42753](https://insights.sbomify.com/CVE-2022-42753/): Cross-site scripting in SalonERP (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45406 is a high-severity SQL injection vulnerability in n/a, published on 14 Jan 2022. 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-45406 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-45406/ (Markdown: https://insights.sbomify.com/CVE-2021-45406/index.md)
```

## Sources

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

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