# CVE-2023-50071: SQL injection in n/a

> Attackers can inject SQL commands via the save_department endpoint to read or modify database contents in the Customer Support System.

- **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:** 29 Dec 2023
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-jr44-f8q6-25rx

## What is CVE-2023-50071?

CVE-2023-50071 is a high-severity SQL injection vulnerability in n/a, published on 29 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sourcecodester Customer Support System 1.0 has multiple SQL injection vulnerabilities in /customer_support/ajax.php?action=save_department via id or name.

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

## Which versions are affected by CVE-2023-50071?

It affects 1 product.


Products: Customer Support System Project Customer Support System.

## How do I fix CVE-2023-50071?

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

## Is CVE-2023-50071 being exploited?

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

Public exploit code:

- Multiple SQL injection vulnerabilities in /customer_support/ajax.php?action=save_department in Customer Support System 1.0 allow authenticated attackers to execute arbitrary SQL commands via id or name. (github_poc): https://github.com/geraldoalcantara/CVE-2023-50071

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50071 and fix it if it is affected.

What it is: CVE-2023-50071 is a high-severity SQL injection vulnerability in n/a, published on 29 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50071 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-2023-50071/ (Markdown: https://insights.sbomify.com/CVE-2023-50071/index.md)
```

## Sources

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

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