# CVE-2020-28133: SQL injection in n/a

> SQL injection in the login functionality allows attackers to bypass authentication and gain client privileges in the Simple Grocery Store Sales And Inventory System.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gqx6-mwq7-ccgm

## What is CVE-2020-28133?

CVE-2020-28133 is a critical SQL injection vulnerability in n/a, published on 17 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SourceCodester Simple Grocery Store Sales And Inventory System 1.0. There was authentication bypass in web login functionality allows an attacker to gain client privileges via SQL injection in sales_inventory/login.php.

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

## Which versions are affected by CVE-2020-28133?

It affects 1 product.


Products: Simple Grocery Store Sales and Inventory Sales Project Simple Grocery Store Sales and Inventory System.

## How do I fix CVE-2020-28133?

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

## Is CVE-2020-28133 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28133 and fix it if it is affected.

What it is: CVE-2020-28133 is a critical SQL injection vulnerability in n/a, published on 17 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28133 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-2020-28133/ (Markdown: https://insights.sbomify.com/CVE-2020-28133/index.md)
```

## Sources

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

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