# CVE-2018-5749: Code injection in n/a

> Remote attackers can execute arbitrary PHP code by injecting malicious input into database connection parameters during installation.

- **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:** 23 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m75p-rvff-x8gj

## What is CVE-2018-5749?

CVE-2018-5749 is a critical code injection vulnerability in n/a, published on 23 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

install.php in Minecraft Servers List Lite before commit c1cd164 and Premium Minecraft Servers List before 2.0.4 does not sanitize input before saving database connection information in connect.php, which might allow remote attackers to execute arbitrary PHP code via the (1) database_server, (2) database_user, (3) database_password, or (4) database_name parameter.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 2 products.


Products: Minecraft Servers List Lite Project Minecraft Servers List Lite, Premium Minecraft Servers List Project Premium Minecraft Servers List.

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

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

## Is CVE-2018-5749 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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