ThinkPHP ↗
Auto-added after CISA flagged ThinkPHP as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Summary iPlain-English security verdict for ThinkPHP, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
ThinkPHP currently scores 62/100 — needs attention. No tracked vulnerabilities are currently known to be exploited in the wild. Patch the open issues below when you can.
The known vulnerabilities
IsItPatched tracks 3 known vulnerabilities in ThinkPHP ThinkPHP disclosed between 2024 and 2025. CVE-2024-44902 is a critical-severity insecure deserialization vulnerability (CVSS 9.8). CVE-2025-63888 is a critical-severity vulnerability (CVSS 9.8). CVE-2025-63889 is a high-severity out-of-bounds read vulnerability (CVSS 7.5). Apply ThinkPHP's latest security update for ThinkPHP to stay protected.
Disclosure trend iNew CVEs published for ThinkPHP each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2024-44902 CRITICAL Insecure deserialization EPSS 4% → see advisory CVE-2025-63888 CRITICAL CWE-98 EPSS 1% → see advisoryGet alerted about ThinkPHP
Be emailed the moment ThinkPHP gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for ThinkPHP — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is ThinkPHP safe and patched?
ThinkPHP currently scores 62/100 — needs attention. No tracked vulnerabilities are currently known to be exploited in the wild. Patch the open issues below when you can.
What should I do about ThinkPHP now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against ThinkPHP's official advisory.
Why is ThinkPHP listed on IsItPatched?
ThinkPHP was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has ThinkPHP been actively exploited?
Yes. CISA added ThinkPHP to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2019-9082. Make sure you are running a patched, supported version of ThinkPHP and confirm it against ThinkPHP's security advisory.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against ThinkPHP's official advisory before you patch or upgrade — ThinkPHP official site ↗