# CVE-2018-10757: SQL injection in n/a

> SQL injection in CSP MySQL User Manager allows attackers to bypass authentication and access data via crafted login credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 5 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hmhg-vrf4-c942

## What is CVE-2018-10757?

CVE-2018-10757 is a critical SQL injection vulnerability in n/a, published on 5 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CSP MySQL User Manager 2.3.1 allows SQL injection, and resultant Authentication Bypass, via a crafted username during a login attempt.

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

## Which versions are affected by CVE-2018-10757?

It affects 1 product.


Products: Csp Mysql User Manager Project Csp Mysql User Manager.

## How do I fix CVE-2018-10757?

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

## Is CVE-2018-10757 being exploited?

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

Public exploit code:

- CSP MySQL User Manager 2.3.1 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-1466](https://insights.sbomify.com/CVE-2014-1466/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10757 and fix it if it is affected.

What it is: CVE-2018-10757 is a critical SQL injection vulnerability in n/a, published on 5 May 2018. 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-2018-10757 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-2018-10757/ (Markdown: https://insights.sbomify.com/CVE-2018-10757/index.md)
```

## Sources

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

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