Vulnerability Database · Packagist · Package report

typo3/cms-install: vulnerability history, versions and safety

typo3/cms-install is a package in the Packagist ecosystem. Vulert records 6 vulnerabilities for it across 12 releases, from Apr 2022 to Jan 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded M3 L3
i
1 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.

Vulert verdict on typo3/cms-install i

Updated on 23 Oct 2026

Careful: one of the 6 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability 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 6 over 2 years · 0 in the last year i
  • Latest disclosure 14 Jan 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 1 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 typo3/cms-install, 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
13.4.2 L1 Yes Details →
v13.4.2 L1 Yes Details →
v12.4.7 L1 Yes Details →
v12.4.6 L1 Yes Details →
v12.4.5 L1 Yes Details →
v12.4.4 L1 Yes Details →
v12.4.3 L1 Yes Details →
v12.4.2 L1 Yes Details →
v12.4.1 L1 Yes Details →
v12.4.0 L1 Yes Details →
v12.3.0 L1 Yes Details →
v12.2.0 L1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 1
  • 2025 1

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

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 typo3/cms-install

Is typo3/cms-install safe to use?

Vulert records 6 vulnerabilities for typo3/cms-install in Packagist: 0 critical, 0 high, 3 medium and 3 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does typo3/cms-install have?

6 vulnerabilities are recorded for typo3/cms-install in the Packagist ecosystem: 0 critical, 0 high, 3 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new typo3/cms-install vulnerabilities disclosed?

0 vulnerabilities were recorded for typo3/cms-install in the last 12 months, and the oldest entry in this database dates to 21 Apr 2022. 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 typo3/cms-install 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 typo3/cms-install for upcoming vulnerabilities?

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