ThinkPHP "noneCms" Remote Code Execution Vulnerability (CVE-2018-20062)

What is affected, what to do

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.

The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

Affected

• ThinkPHP noneCms eq 1.3.0..1.3.0

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

Response and mitigation

1. 01

   Runbook step 1

   Immediate response (0-24 h)

   • Enumerate all internet-facing instances of NoneCms 1.3.0 and ThinkPHP-based applications (particularly ThinkPHP 5.0.x < 5.0.23 and 5.1.x < 5.1.31). Fingerprint via /index.php?s= paths and the X-Powered-By: ThinkPHP response header.
   • Pull affected instances behind a WAF or take them offline until patched. An unauthenticated network-reachable RCE justifies a temporary takedown.
   • Upgrade the underlying framework to ThinkPHP ≥ 5.0.23 or ≥ 5.1.31. NoneCms 1.3.0 is effectively unmaintained — plan migration to a supported CMS; until then, backport the framework fix manually into thinkphp/library/think/App.php and Request.php (sanitise the s parameter, forbid invokeMethod on arbitrary classes).
   • Hunt for compromise of the web process account (www-data, php-fpm, nginx): unexpected outbound connections, new files in public/ or runtime/, recently modified .php files, cron entries, and authorized_keys for the web user.
   • Rotate database credentials and API keys stored in application/database.php and .env if any affected host is to be considered potentially compromised.
2. 02

   Runbook step 2

   Mitigation layers

   • WAF rule: block HTTP requests whose query string or body contains s= combined with think\Request, invokefunction, call_user_func, filter=phpinfo|system|exec|assert|eval, or \\think\\app (case-insensitive, URL-decoded).
   • Web server config: remove rewrite rules that enable index.php?s= style routing; enforce explicit path-info routing instead. Example nginx snippet: if ($args ~* "s=.*think\\\\") { return 403; }.
   • Network segmentation: restrict outbound traffic from the web tier to a defined allow-list (DB, update mirrors). This blocks webshell stagers and C2 callbacks even if exploitation succeeds.
   • PHP hardening in php.ini: set disable_functions = exec,passthru,shell_exec,system,proc_open,popen,curl_exec,assert,eval and constrain open_basedir to the application directory.
   • Least privilege on the filesystem: the web user must not own or write to code directories (application/, thinkphp/, public/*.php); only runtime/ and dedicated upload paths remain writable, with PHP execution disabled there (php_admin_flag engine off).
   • Front with a reverse proxy or API gateway and whitelist only required URL paths. Anything matching s=index/\think\... is dropped at the perimeter.
3. 03

   Runbook step 3

   Detection rules

   • Web access logs (Zeek http.log, nginx, Apache): search for s=.*think\\\\Request|invokefunction|call_user_func_array|filter=(phpinfo|system|exec|assert|md5). Sigma shape: selection: cs-uri-query|contains: ['think\\\\Request', 'invokefunction', 'filter=phpinfo'].
   • Suricata/Snort: Emerging Threats signatures for ThinkPHP RCE have shipped since 2018 (SIDs around 2026731-2026734 and follow-ups) — verify they are enabled and promote from alert to drop after tuning.
   • EDR/auditd on Linux: process ancestry nginx|httpd|php-fpm → sh|bash|python|perl|wget|curl is anomalous for a CMS appliance. KQL-style: DeviceProcessEvents | where InitiatingProcessFileName in ('php-fpm','httpd','nginx') and FileName in ('sh','bash','curl','wget','python','perl').
   • Filesystem monitoring: new or modified .php files under public/, runtime/, and upload directories — auditd rule -w /var/www/ -p wa -k webshell.
   • Network telemetry (Zeek conn.log, NetFlow): outbound connections from the web tier to non-whitelisted IPs on ports 80/443/4444/1337 — a common signature of reverse shells and coin-miner payloads observed in campaigns against ThinkPHP.

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2

NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

Read in glossary

Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).

CRA

The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

Read in glossary

Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.

ISO/IEC 27001

ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

Read in glossary

Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

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.

Source: NVD (NIST), cvelistv5, CISA KEV Catalog

Vendors and products

• ThinkPHP ThinkPHP noneCms

References & sources

• github.comnangge/noneCms/issues/21x_refsource_MISC, Exploit, Third-party advisory
• packetstormsecurity.comfiles/157218/ThinkPHP-5.0.23-Remote-Code-Execution.htmlx_refsource_MISC, Exploit, Third-party advisory, Vulnerability database
• cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2018-20062government-resource, US government resource

Linked advisories

• Exposed Vite servers are being probed for AWS and Azure credentialsCSO Online15.09.2026