Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

thinkphp

About This Vendor

thinkphp is a technology vendor producing software and infrastructure products. As a software provider, thinkphp's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of thinkphp's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 26 known vulnerabilities from thinkphp. This includes 19 critical-severity issues and 6 high-severity issues that represent significant risk. These vulnerabilities affect 3 distinct products across thinkphp's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2018 through 2025, reflecting sustained security scrutiny over multiple years. Organizations deploying thinkphp products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.

ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-2018-10225 2018-04-19 2024-11-21 9.8 7.5 Likely
CVE-2018-16385 2018-09-03 2024-11-21 9.8 7.5 Likely
CVE-2018-17566 2018-09-26 2024-11-21 9.8 7.5 Likely
CVE-2018-18529 2018-10-19 2024-11-21 9.8 7.5 Likely
CVE-2018-18530 2018-10-19 2024-11-21 9.8 7.5 Likely
CVE-2018-18546 2018-10-21 2024-11-21 9.8 7.5 Likely
CVE-2019-9082 2019-02-24 2025-12-09 8.8 9.3 Likely
CVE-2020-20120 2021-09-28 2024-11-21 9.8 7.5 Likely
CVE-2021-36564 2021-12-06 2024-11-21 9.8 7.5 Likely
CVE-2021-36567 2021-12-06 2024-11-21 9.8 10.0 Likely
CVE-2021-44350 2021-12-15 2024-11-21 9.8 7.5 Likely
CVE-2021-44892 2022-02-10 2024-11-21 8.8 6.5 Likely
CVE-2022-25481 2022-03-21 2024-11-21 7.5 5.0 Likely
CVE-2021-23592 2022-05-06 2024-11-21 7.7 7.5 Likely
CVE-2022-33107 2022-06-29 2024-11-21 9.8 7.5 Likely
CVE-2022-38352 2022-09-15 2024-11-21 9.8 - -
CVE-2022-44289 2022-12-06 2025-04-23 8.8 - -
CVE-2022-47945 2022-12-23 2025-04-15 9.8 - -
CVE-2022-45982 2023-02-08 2025-03-25 9.8 - -
CVE-2024-34467 2024-05-04 2025-06-17 6.1 - -
CVE-2024-44902 2024-09-09 2024-09-20 9.8 - -
CVE-2024-48112 2024-10-30 2025-06-17 9.8 - -
CVE-2025-50706 2025-08-05 2025-08-14 9.8 - -
CVE-2025-50707 2025-08-05 2025-08-14 9.8 - -
CVE-2025-63888 2025-11-20 2025-11-25 9.8 - -
CVE-2025-63889 2025-11-20 2025-11-25 7.5 - -

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for thinkphp by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with thinkphp's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.