Security readout for executives and security teams
Plain-English summary
ThinkPHP versions 5.0.23 and 5.1.31 are reported vulnerable to unauthenticated remote code execution. An internet-facing vulnerable application could let an attacker run PHP code with the web application’s privileges. This is a critical issue for exposed ThinkPHP deployments, even though the provided sources do not show confirmed active exploitation.
Executive priority
Treat as urgent for any public-facing ThinkPHP application. The issue enables unauthenticated code execution and has public exploit information. If ThinkPHP is not present, priority drops to confirming absence through asset and dependency inventory.
Technical view
The vulnerability involves ThinkPHP routing parameters and the invokefunction mechanism, allowing unauthenticated attackers to execute arbitrary PHP code via crafted requests to index.php. The CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction required. Public exploit reference exists, but KEV status is false in the provided bundle.
Likely exposure
Highest risk applies to public-facing applications running ThinkPHP 5.0.23 or 5.1.31. Internal deployments are still exposed if reachable by untrusted users or compromised systems. Confirm exposure by inventorying ThinkPHP framework versions and externally reachable routes.
Exploitation context
The source bundle includes an ExploitDB reference, indicating public exploit information exists. However, the bundle does not cite CISA KEV listing or another source confirming active exploitation. Treat internet-facing affected systems as urgent due to unauthenticated RCE characteristics.
Researcher notes
CVE data lists ThinkPHP 5.0.23 and 5.1.31 as affected. The description centers on invokefunction abuse through routing parameters. CWE-639 is listed, though the described impact is remote code execution. No fixed version is provided in the supplied sources, so remediation should be tied to vendor guidance.
Mitigation direction
- Identify applications using ThinkPHP 5.0.23 or 5.1.31.
- Check official ThinkPHP guidance for fixed versions or vendor-recommended remediation.
- Prioritize upgrading or removing affected ThinkPHP versions where confirmed.
- Restrict public access to affected applications until remediation is complete.
- Review web application logs for suspicious requests targeting index.php parameters.
Validation and detection
- Inventory application dependencies and confirm the ThinkPHP framework version.
- Map which affected applications are internet-facing or reachable by untrusted users.
- Review vendor and advisory pages for updated fix information.
- Check logs for abnormal requests involving routing or function invocation parameters.
- Validate remediation by confirming affected versions are no longer deployed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-25270 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-45978CVE reference · exploit
- Official Product HomepageCVE reference · product
- Product ReferenceCVE reference · product
- VulnCheck Advisory: ThinkPHP 5.0.23 Remote Code Execution via invokefunctionCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.