Threats / ThinkPHP / CVE-2018-20062
CVE-2018-20062
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
ThinkPHP noneCms vulnerability
ThinkPHP noneCms contains an unspecified vulnerability allowing remote code execution via crafted filter parameter manipulation.
Verdict
Today item — known-exploited.
An unauthenticated attacker can execute arbitrary code on affected noneCms instances by exploiting improper input validation in the filter parameter. This vulnerability is actively exploited in the wild with high exploit probability.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
69 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.9953 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: ThinkPHP, noneCms. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request containing a specially formatted filter parameter to bypass input validation.
Business
The application fails to properly sanitize user-supplied filter input, creating an entry point for code injection.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I inject PHP code or system commands through the filter parameter to achieve remote code execution on the server.
Business
The server executes attacker-controlled code with the privileges of the web application process.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access, exfiltrate sensitive data, or pivot to internal systems from the compromised web server.
Business
Complete compromise of application confidentiality, integrity, and availability; potential lateral movement to backend infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05