CVE-2019-25782
- Published18 Nov 2026
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.
CVSS 4.0 breakdown
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml
- https://github.com/top-think/framework/commit/4a4b5e64fa4c46f851b4004005bff5f3196de003
- https://github.com/vulhub/vulhub/tree/master/thinkphp/5.0.23-rce
- https://packetstorm.news/files/id/157218/
- https://www.exploit-db.com/exploits/46150
- 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
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2019-25782 being actively exploited?
CVE-2019-25782 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.68%.
How severe is CVE-2019-25782?
CVE-2019-25782 has a CVSS 4.0 base score of 9.3, rated critical. EPSS estimates a 0.68% probability of exploitation.
How do I fix CVE-2019-25782?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2019-25782 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. The CVSS 4.0 base score is shown where the NVD has one, otherwise CVSS 3.1.