CVE-2025-50706: Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% 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
1. Immediate assessment of all web applications and services using ThinkPHP framework version 5.1 to identify vulnerable instances. 2. If possible, temporarily disable or restrict access to the 'routecheck' function or related routing features until a patch is available. 3. Implement web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the routecheck function or unusual routing patterns. 4. Employ strict input validation and sanitization at the application level to reduce the risk of injection attacks. 5. Monitor web server and application logs for anomalous activity indicative of exploitation attempts. 6. Segregate and harden web servers to limit lateral movement in case of compromise. 7. Stay updated with vendor advisories for patches or official mitigations and apply them promptly once released. 8. Conduct penetration testing focused on this vulnerability to validate defenses. 9. Educate development and security teams about the risk and signs of exploitation to improve detection and response.
Description
An issue in thinkphp v.5.1 allows a remote attacker to execute arbitrary code via the routecheck function