Is topthink/framework 5.1 vulnerable?
Composer · 45 releases from 5.1.0 to 5.1.42 · latest topthink/framework is 8.1.4 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. topthink/framework 5.1.42, the last 5.1 release, is affected by 7 known security advisories (6 critical, 1 medium), including CVE-2022-47945, CVE-2022-38352, CVE-2022-33107. 6 more affect earlier 5.1.x releases. At least one has no fixed release yet.
Is your project on an affected topthink/framework?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting topthink/framework 5.1.42
ThinkPHP Cross-Site Scripting Vulnerability
- Affected
- >=8.0.0 <8.0.4 · >=6.1.0 <6.1.5 · <6.0.17
- Fixed in
- 6.0.17, 6.1.5, 8.0.4
ThinkPHP Framework vulnerable to remote code execution
- Affected
- <6.0.14
- Fixed in
- 6.0.14
ThinkPHP deserialization vulnerability
- Affected
- <=6.0.13
- Fixed in
- No fix released
Deserialization of Untrusted Data in topthink/framework
- Affected
- <=6.0.12
- Fixed in
- No fix released
Deserialization of Untrusted Data in topthink/framework
- Affected
- <6.0.12
- Fixed in
- 6.0.12
Deserialization of Untrusted Data in topthink/framework
- Affected
- <6.0.9
- Fixed in
- 6.0.9
Deserialization of Untrusted Data in topthink/framework
- Affected
- <=6.0.8
- Fixed in
- No fix released
Fixed within 5.1.x, affecting earlier releases
ThinkPHP Path Traversal Vulnerability
- Affected
- <=5.1.41
- Fixed in
- No fix released
Thinkphp has a code logic error
- Affected
- <=5.0.24 · >=5.1 <=5.1.41
- Fixed in
- No fix released
ThinkPHP SQL Injection vulnerability
- Affected
- <5.1.23
- Fixed in
- 5.1.23
ThinkPHP SQL injection vulnerability
- Affected
- 5.1.24
- Fixed in
- No fix released
ThinkPHP SQLi Vulnerability
- Affected
- <=5.1.25
- Fixed in
- No fix released
ThinkPHP5 SQL Injection vulnerability
- Affected
- >=5.0 <=5.1.22
- Fixed in
- No fix released
Every topthink/framework 5.1.x release
Affected: 5.1.0 to 5.1.42. Latest topthink/framework: 8.1.4.
| Version | Known advisories |
|---|---|
| topthink/framework 5.1.42 | CVE-2024-34467, CVE-2022-47945, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.41 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.40 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.39 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.38.1 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.38 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.37.1 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.37 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.36 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.35 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.34 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.33 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.32 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.31 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.30 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.29 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.28 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.27 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.26 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.25 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-18530, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.24 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-17566, CVE-2018-18530, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.23 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-18530, CVE-2021-23592, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.22 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.21 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.20 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.19 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.18 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.17 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.16 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.15 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.14 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.13 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.12 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.11 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.10 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.9 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.8 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.7 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.6 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.5 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.4 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.3 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.2 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.1 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
| topthink/framework 5.1.0 | CVE-2025-50706, CVE-2024-34467, CVE-2022-47945, CVE-2022-44289, CVE-2022-38352, CVE-2022-33107, CVE-2018-16385, CVE-2018-18530, CVE-2021-23592, CVE-2021-44350, CVE-2021-36564, CVE-2021-36567 |
Which of your client projects are still on topthink/framework 5.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact topthink/framework version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other topthink/framework versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.