# CVE-2024-40392: SQL injection in n/a

> An attacker can exploit a SQL injection vulnerability in the addnew.php script to read or modify database contents.

- **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:** 16 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v65v-9xgh-293p

## What is CVE-2024-40392?

CVE-2024-40392 is a critical SQL injection vulnerability in n/a, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SourceCodester Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code 1.0 was discovered to contain a SQL injection vulnerability via the name parameter under addnew.php.

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

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

It affects 1 product.


Products: Fkgeo Pharmacy\/Medical Store Point of Sale System.

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

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

## Is CVE-2024-40392 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40392 is a critical SQL injection vulnerability in n/a, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40392 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-2024-40392/ (Markdown: https://insights.sbomify.com/CVE-2024-40392/index.md)
```

## Sources

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

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