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

> Attackers can execute arbitrary PHP code by uploading malicious files via the file manager plugin in Frog CMS.

- **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:** 11 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j2hq-64gw-xw35

## What is CVE-2018-20775?

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

### Official description

admin/?/plugin/file_manager in Frog CMS 0.9.5 allows PHP code execution by creating a new .php file containing PHP code, and then visiting this file under the public/ URI.

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

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

It affects 1 product.


Products: Frog Cms Project Frog Cms.

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

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

## Is CVE-2018-20775 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4912](https://insights.sbomify.com/CVE-2014-4912/): File upload in n/a (critical 9.8)
- [CVE-2018-8908](https://insights.sbomify.com/CVE-2018-8908/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-20776](https://insights.sbomify.com/CVE-2018-20776/): Information disclosure in n/a (high 7.5)
- [CVE-2018-20772](https://insights.sbomify.com/CVE-2018-20772/): Code injection in n/a (high 7.2)
- [CVE-2018-20773](https://insights.sbomify.com/CVE-2018-20773/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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