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

> Remote attackers can execute arbitrary PHP code via the host parameter in the install URI of LAOBANCMS.

- **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:** 12 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pqrv-4w4w-mgx5

## What is CVE-2018-19220?

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

### Official description

An issue was discovered in LAOBANCMS 2.0. It allows remote attackers to execute arbitrary PHP code via the host parameter to the install/ URI.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Laobancms Laobancms.

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

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

## Is CVE-2018-19220 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18166](https://insights.sbomify.com/CVE-2020-18166/): File upload in n/a (critical 9.8)
- [CVE-2018-19328](https://insights.sbomify.com/CVE-2018-19328/): Path traversal in n/a (critical 9.8)
- [CVE-2018-19221](https://insights.sbomify.com/CVE-2018-19221/): SQL injection in n/a (critical 9.8)
- [CVE-2018-19222](https://insights.sbomify.com/CVE-2018-19222/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-19225](https://insights.sbomify.com/CVE-2018-19225/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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