VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

topthink/thinkphp: vulnerability history, versions and safety

topthink/thinkphp is a package in the Packagist ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, from Sep 2021 to Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all topthink/thinkphp vulnerabilities

Vulert verdict on topthink/thinkphp i

Updated on 23 Oct 2026

Careful: 2 of the 2 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 2 vulnerabilities on record across 3 years, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 2 over 3 years · 0 in the last year i
  • Latest disclosure 30 Oct 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for topthink/thinkphp, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
3.2.3 C1 No Details →
3.2.2 C1 No Details →

Newest 2 of 2 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for topthink/thinkphp

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-20120: SQL Injection in topthink/thinkphp 9.8 critical No fix published 30 Sep 2021
CVE-2024-48112: ThinkPHP Deserialization Vulnerability Leading to Arbitrary Code Execution 9.8 high No fix published 30 Oct 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About topthink/thinkphp

Is topthink/thinkphp safe to use?

Vulert records 2 vulnerabilities for topthink/thinkphp in Packagist: 1 critical, 1 high, 0 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does topthink/thinkphp have?

2 vulnerabilities are recorded for topthink/thinkphp in the Packagist ecosystem: 1 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new topthink/thinkphp vulnerabilities disclosed?

0 vulnerabilities were recorded for topthink/thinkphp in the last 12 months, and the oldest entry in this database dates to 30 Sep 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of topthink/thinkphp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor topthink/thinkphp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the topthink/thinkphp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.