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

> Remote attackers can execute arbitrary PHP code via eval injection in YzmCMS member content initialization.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9g7c-fg2x-x4jg

## What is CVE-2018-8756?

CVE-2018-8756 is a high-severity code injection vulnerability in n/a, published on 18 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Eval injection in yzmphp/core/function/global.func.php in YzmCMS v3.7.1 allows remote attackers to achieve arbitrary code execution via PHP code in the POST data of an index.php?m=member&c=member_content&a=init request.

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

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

It affects 1 product.


Products: Yzmcms Yzmcms.

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

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

## Is CVE-2018-8756 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11554](https://insights.sbomify.com/CVE-2018-11554/): Information disclosure in n/a (critical 9.8)
- [CVE-2022-23383](https://insights.sbomify.com/CVE-2022-23383/): Missing authorization in n/a (critical 9.1)
- [CVE-2020-23595](https://insights.sbomify.com/CVE-2020-23595/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-23384](https://insights.sbomify.com/CVE-2022-23384/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-23888](https://insights.sbomify.com/CVE-2022-23888/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8756 is a high-severity code injection vulnerability in n/a, published on 18 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8756 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-8756/ (Markdown: https://insights.sbomify.com/CVE-2018-8756/index.md)
```

## Sources

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

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