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

> Attackers can inject arbitrary PHP code into cache files via the template parameter, leading to remote code execution on PHPCMS installations.

- **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:** 9 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p498-q357-m3p7

## What is CVE-2018-19127?

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

### Official description

A code injection vulnerability in /type.php in PHPCMS 2008 allows attackers to write arbitrary content to a website cache file with a controllable filename, leading to arbitrary code execution. The PHP code is sent via the template parameter, and is written to a data/cache_template/*.tpl.php file along with a "<?php function " substring.

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

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

It affects 1 product.


Products: Phpcms Phpcms.

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

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

## Is CVE-2018-19127 being exploited?

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

Public exploit code:

- https://github.com/ab1gale/phpcms-2008-CVE-2018-19127 (github_poc): https://github.com/ab1gale/phpcms-2008-CVE-2018-19127
- PHPCMS 2008 - Remote Code Execution via Template Injection (nuclei): http/cves/2018/CVE-2018-19127.yaml

## Other vulnerabilities in n/a

- [CVE-2020-22199](https://insights.sbomify.com/CVE-2020-22199/): SQL injection in n/a (critical 9.8)
- [CVE-2020-22203](https://insights.sbomify.com/CVE-2020-22203/): SQL injection in n/a (critical 9.8)
- [CVE-2020-22201](https://insights.sbomify.com/CVE-2020-22201/): Code injection in n/a (high 8.8)
- [CVE-2008-0513](https://insights.sbomify.com/CVE-2008-0513/): Path traversal in n/a (high 7.8)
- [CVE-2018-14940](https://insights.sbomify.com/CVE-2018-14940/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19127 is a critical code injection vulnerability in n/a, published on 9 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19127 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-2018-19127/ (Markdown: https://insights.sbomify.com/CVE-2018-19127/index.md)
```

## Sources

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

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