# CVE-2024-4826: SQL injection vulnerability in Simple PHP Shopping Cart

> An attacker can retrieve all database information via SQL injection in the category_id parameter of Simple PHP Shopping Cart.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-wx6j-6xmp-c56f

## What is CVE-2024-4826?

CVE-2024-4826 is a critical SQL injection vulnerability in Asaancart Simple PHP Shopping Cart, published on 16 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in Simple PHP Shopping Cart affecting version 0.9. This vulnerability could allow an attacker to retrieve all the information stored in the database by sending a specially crafted SQL query, due to the lack of proper sanitisation of the category_id parameter in the category.php file.

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

## Which versions are affected by CVE-2024-4826?


## How do I fix CVE-2024-4826?

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

## Is CVE-2024-4826 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4826 and fix it if it is affected.

What it is: CVE-2024-4826 is a critical SQL injection vulnerability in Asaancart Simple PHP Shopping Cart, published on 16 May 2024. 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-2024-4826 in the wild and no public exploit code.

Affected product: Asaancart Simple PHP Shopping Cart. 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-2024-4826/ (Markdown: https://insights.sbomify.com/CVE-2024-4826/index.md)
```

## Sources

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

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