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

> Admin users can execute arbitrary code via the varvalue field in PHPMyWind's web configuration interface.

- **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:** 17 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4vf9-q573-42vp

## What is CVE-2018-17131?

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

### Official description

admin/web_config.php in PHPMyWind 5.5 allows Admin users to execute arbitrary code via the varvalue field.

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

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

It affects 1 product.


Products: Phpmywind Phpmywind.

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

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

## Is CVE-2018-17131 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-21060](https://insights.sbomify.com/CVE-2020-21060/): SQL injection in n/a (high 8.8)
- [CVE-2020-21400](https://insights.sbomify.com/CVE-2020-21400/): SQL injection in n/a (high 7.2)
- [CVE-2021-39503](https://insights.sbomify.com/CVE-2021-39503/): Code injection in n/a (high 7.2)
- [CVE-2020-18885](https://insights.sbomify.com/CVE-2020-18885/): Command injection in n/a (high 7.2)
- [CVE-2020-18886](https://insights.sbomify.com/CVE-2020-18886/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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