CVE-2019-25782 is a critical code injection flaw in ThinkPHP 5.0.x that lets unauthenticated attackers run arbitrary system commands with a crafted POST request. The NVD record lists versions 5.0.0 through 5.0.23 as affected.
What Is It
CVE-2019-25782 is a code injection vulnerability in the TopThink ThinkPHP framework. An unauthenticated attacker sets _method=__construct in POST data, which overwrites the Request object's filter property. The NVD record says attackers can send POST requests to endpoints reached via ?s=captcha or ?s=index/index/index, supplying filter[]=system and server[REQUEST_METHOD] values to run arbitrary system commands.
VulnCheck assigned the CVE and classifies the weakness as CWE-470 (Use of Externally-Controlled Input to Select Classes or Code). NVD published the record on 2026-11-18, and its status is currently "Received."
Why It Matters
- Severity: CVSS 3.1 base score 9.8 (CRITICAL), vector
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVSS 4.0 score is 9.3 (CRITICAL). - No barriers: Exploitation works over the network with low complexity. It needs no privileges and no user interaction.
- Exploitation observed: The NVD description says the Shadowserver Foundation first observed exploitation evidence on 2023-10-14.
- CISA SSVC: Exploitation is rated "poc", automatable "yes" and technical impact "total".
- Public exploit material: The references include Exploit-DB, Packet Storm, a Vulhub environment and a Nuclei template.
- KEV status: The supplied CISA KEV entry is empty, so KEV does not confirm active exploitation for this CVE.
What's Vulnerable
- Vendor: TopThink
- Product: ThinkPHP
- Affected versions (per NVD): 5.0.0 up to but not including 5.0.24
The CVE record lists versions outside this range as unaffected. NVD does not yet list any affected CPEs.
Patch Status
According to the NVD record, versions before 5.0.24 are affected. However, the cited sources don't agree on the upper bound. One VulnCheck advisory URL gives the range as 5.0.0–5.0.24, which suggests 5.0.24 may also be affected. The other gives it as 5.0.0–5.0.23. The supplied data does not settle which version first contains the fix. The references include an upstream fix commit in the top-think/framework repository. Recommended actions:
- Upgrade any ThinkPHP 5.0.x deployment to the latest available release, and confirm that the build includes the upstream fix commit. Don't assume 5.0.24 alone is enough.
- Inventory older ThinkPHP builds, check whether any are exposed to the internet, and plan to move them to a maintained release.
The supplied data does not include a CISA required action or due date.