CVE-2025-50707: thinkphp3 · Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should immediately identify any usage of ThinkPHP3 version 3.2.5 within their environments. 2) Restrict access to vulnerable applications by IP whitelisting or VPN-only access where feasible. 3) Conduct thorough code reviews and input validation improvements around the index.php component to prevent injection vectors. 4) Monitor logs for anomalous activity, such as unexpected command execution or unusual HTTP requests. 5) Plan and prioritize migration to newer, supported versions of ThinkPHP or alternative frameworks with active security maintenance. 6) Employ network segmentation to limit the impact of any potential compromise. 7) Stay alert for official patches or security advisories from ThinkPHP maintainers and apply updates promptly once available.
Description
An issue in thinkphp3 v.3.2.5 allows a remote attacker to execute arbitrary code via the index.php component