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

> Remote attackers can execute arbitrary PHP code in YUNUCMS if the installation lock file is missing, allowing full system compromise.

- **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:** 11 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2q6f-jmhv-h8gr

## What is CVE-2018-19180?

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

### Official description

statics/app/index/controller/Install.php in YUNUCMS 1.1.5 (if install.lock is not present) allows remote attackers to execute arbitrary PHP code by placing this code in the index.php?s=index/install/setup2 DB_PREFIX field, which is written to database.php.

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

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

It affects 1 product.


Products: Yunucms Yunucms.

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

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

## Is CVE-2018-19180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19181](https://insights.sbomify.com/CVE-2018-19181/): Path traversal in n/a (high 7.5)
- [CVE-2020-18445](https://insights.sbomify.com/CVE-2020-18445/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-5310](https://insights.sbomify.com/CVE-2019-5310/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-5311](https://insights.sbomify.com/CVE-2019-5311/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-17322](https://insights.sbomify.com/CVE-2018-17322/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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