CVE
TopThink ThinkPHP unauthenticated remote code execution in request class
Affects ThinkPHP 5.0.0 through 5.0.23, where the _method handling in Request.php allows remote code execution. Fixed in 5.0.24.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 5.0.24
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.0.24.
Summary
ThinkPHP 5.0.0 before 5.0.24 contains a code injection vulnerability that allows unauthenticated attackers to execute commands by setting _method=__construct in POST data to overwrite the Request filter property. Attackers can send POST requests to endpoints reached via ?s=captcha or ?s=index/index/index with filter[]=system and server[REQUEST_METHOD] values to execute arbitrary system commands. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.
Who should check
Teams running ThinkPHP 5.0.x web applications, including 5.0.23, which the advisory names as affected.
“ThinkPHP 5.0.23 is susceptible to remote code execution.”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.0.24.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2019-25782 (ThinkPHP 5.0.0 < 5.0.24 RCE via _method construct in Request.php), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2019-25782 (entry last updated 2026-11-18):
Affected:
- TopThink ThinkPHP: from 5.0.0, fixed in 5.0.24
Fixed versions: 5.0.24.
Conditions (all must be true for the bug to be hit):
- Running ThinkPHP 5.0.23 (the affected version named in the advisory) (source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2019-25782 is not listed as of cve.now's last read.
This KEV status is for CVE-2019-25782 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/top-think/framework/commit/4a4b5e64fa4c46f851b4004005bff5f3196de003
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml
- https://www.vulncheck.com/advisories/thinkphp-5.0.0-5.0.23-rce-via-method-construct-in-request-php
- https://www.vulncheck.com/advisories/thinkphp-5.0.0-5.0.24-rce-via-method-construct-in-request-php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2019-25782
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2019-25782"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- TopThink ThinkPHP
From 5.0.0 · fixed in 5.0.24
Evidence 9
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2019-25782 |
| Record | NVD · CVE-2019-25782 |
| Public exploit code 4Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · vulhub/vulhub · tree/master/thinkphp/5.0.23-rce |
| Exploit | Exploit-DB · Exploit EDB-46150 |
| Exploit | packetstorm.news · files/id/157218 |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml |
| Other links 3 | |
| Patch | GitHub · top-think/framework · Commit 4a4b5e64 |
| Link | vulncheck.com · advisories/thinkphp-5.0.0-5.0.23-rce-via-method-construct-in-request-php |
| Link | vulncheck.com · advisories/thinkphp-5.0.0-5.0.24-rce-via-method-construct-in-request-php |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2019-25782
Is CVE-2019-25782 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The _method handling in ThinkPHP's Request.php can be abused to achieve remote code execution, so an attacker could run code on the server. The advisory says this could let an attacker execute malware, obtain sensitive information, modify data, or gain full control of the compromised system.Source: github.com
Which versions are affected by CVE-2019-25782?
ThinkPHP: from 5.0.0 before 5.0.24.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 5.0.0 up to but not including 5.0.24 are in the affected range, and the advisory names ThinkPHP 5.0.23 as susceptible. To check a installation, identify which ThinkPHP 5.0.x release is in use and compare it with that range.Source: github.com
How do I fix CVE-2019-25782?
Upgrade ThinkPHP to 5.0.24 or later, which is the fixed version for this range.Source: github.com