# CVE-2018-20062: ThinkPHP "noneCms" Remote Code Execution

> Remote attackers can execute arbitrary PHP code in NoneCms via the filter parameter in the ThinkPHP framework.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-gf7c-4w4p-7cm5

## What is CVE-2018-20062?

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

### Official description

An issue was discovered in NoneCms V1.3. thinkphp/library/think/App.php allows remote attackers to execute arbitrary PHP code via crafted use of the filter parameter, as demonstrated by the s=index/\think\Request/input&filter=phpinfo&data=1 query string.

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

It affects 1 product.


Products: 5none Nonecms.

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

No fix has been published for CVE-2018-20062 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2018-20062 being exploited?

Yes. Attackers have exploited CVE-2018-20062 in the wild since at least 3 Nov 2021.

Public exploit code:

- thinkphp5.*Rce CVE-2018-20062 (github_poc): https://github.com/NS-Sp4ce/thinkphp5.XRce
- https://github.com/yilin1203/CVE-2018-20062 (github_poc): https://github.com/yilin1203/CVE-2018-20062
- RedArrow3.2 是一款用于渗透测试ThinkPHP 5.0.23 远程命令执行漏洞(CVE-2018-20062)的图形化工具。 (github_poc): https://github.com/shenhui35/RedArrow
- ThinkPHP Multiple PHP Injection RCEs (metasploit)
- ThinkPHP - Multiple PHP Injection RCEs (Metasploit) (exploitdb)
- ThinkPHP 5.0.23 RCE Vulnerability PoC - CVE-2018-20062 (github_poc): https://github.com/0xRar/ThinkPHP5_RCE

## Other vulnerabilities in n/a

- [CVE-2018-7219](https://insights.sbomify.com/CVE-2018-7219/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-18646](https://insights.sbomify.com/CVE-2020-18646/): Information disclosure in n/a (high 7.5)
- [CVE-2020-18647](https://insights.sbomify.com/CVE-2020-18647/): Information disclosure in n/a (high 7.5)
- [CVE-2018-6029](https://insights.sbomify.com/CVE-2018-6029/): Server-side request forgery in n/a (high 7.5)
- [CVE-2019-16721](https://insights.sbomify.com/CVE-2019-16721/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20062 is a critical code injection vulnerability in n/a, published on 11 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-20062 in the wild since at least 3 Nov 2021.

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-20062/ (Markdown: https://insights.sbomify.com/CVE-2018-20062/index.md)
```

## Sources

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

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