Vulnerability Database · Packagist · Package report

contao/core: vulnerability history, versions and safety

contao/core is a package in the Packagist ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Apr 2022 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C1 H2 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 contao/core i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 15 May 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 2 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 15 May 2024 i
  • Highest CVSS 9.0 i
  • With no published fix 0 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 contao/core, 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.5.31 M1 Yes Details →
3.5.30 M1 Yes Details →
3.5.29 M1 Yes Details →
3.5.28 M1 Yes Details →
3.5.27 M1 Yes Details →
3.5.26 M1 Yes Details →
3.5.25 M1 Yes Details →
3.5.24 M1 Yes Details →
3.5.23 M1 Yes Details →
3.5.22 M1 Yes Details →
3.5.21 M1 Yes Details →
3.5.20 M1 Yes Details →
3.5.19 M1 Yes Details →
3.5.18 M1 Yes Details →
3.5.17 M1 Yes Details →
3.5.16 M1 Yes Details →
3.5.15 M1 Yes Details →
3.5.14 M1 Yes Details →
3.5.13 M1 Yes Details →
3.5.12 M1 Yes Details →
3.5.11 M1 Yes Details →
3.5.10 M1 Yes Details →
3.5.9 M1 Yes Details →
3.5.8 M1 Yes Details →
3.5.7 M1 Yes Details →
3.5.6 M1 Yes Details →
3.5.5 M1 Yes Details →
3.5.4 M1 Yes Details →
3.5.3 M1 Yes Details →
3.5.2 M1 Yes Details →
3.5.1 M1 Yes Details →
3.5.0 M1 Yes Details →
3.5.0-RC1 M1 Yes Details →
3.5.0-beta1 M1 Yes Details →
3.4.5 M1 Yes Details →
3.4.4 M1 Yes Details →
3.4.3 M2 Yes Details →
3.4.2 M2 Yes Details →
3.4.1 M2 Yes Details →
3.4.0 M2 Yes Details →
3.4.0-RC1 M1 Yes Details →
3.4.0-beta1 M1 Yes Details →
3.3.7 M1 Yes Details →
3.3.6 M1 Yes Details →
3.3.5 M1 Yes Details →
3.3.4 M1 Yes Details →
3.3.3 M1 Yes Details →
3.3.2 M1 Yes Details →
3.3.1 M1 Yes Details →
3.3.0 M1 Yes Details →
3.3.0-RC2 M1 Yes Details →
3.3.0-RC1 M1 Yes Details →
3.3.0-beta1 M1 Yes Details →
3.2.21 M1 Yes Details →
3.2.20 M1 Yes Details →
3.2.19 M1 Yes Details →
3.2.18 M1 Yes Details →
3.2.17 M1 Yes Details →
3.2.16 M1 Yes Details →
3.2.15 M1 Yes Details →
3.2.14 M1 Yes Details →
3.2.13 M1 Yes Details →
3.2.12 M1 Yes Details →
3.2.11 M1 Yes Details →
3.2.10 M1 Yes Details →
3.2.9 M1 Yes Details →
3.2.8 M1 Yes Details →
3.2.7 M1 Yes Details →
3.2.6 M1 Yes Details →
3.2.5 M1 Yes Details →
3.2.4 M1 Yes Details →
3.2.3 M1 Yes Details →
3.2.2 M1 Yes Details →
3.2.1 M1 Yes Details →
3.2.0 M1 Yes Details →
3.2.RC1 M1 Yes Details →
3.2.beta2 M1 Yes Details →
3.2.beta1 M1 Yes Details →
3.1.5 M1 Yes Details →
3.1.4 M1 Yes Details →
3.1.3 M1 Yes Details →
3.1.2 M1 Yes Details →
3.1.1 M1 Yes Details →
3.1.0 M1 Yes Details →
3.1.RC1 M1 Yes Details →
3.1.beta1 M1 Yes Details →
3.0.6 M1 Yes Details →
3.0.5 M1 Yes Details →
3.0.4 M1 Yes Details →
3.0.3 M1 Yes Details →
3.0.2 M1 Yes Details →
3.0.1 M1 Yes Details →
3.0.0 M1 Yes Details →
2.11.16 C1 Yes Details →
2.11.15 C1 Yes Details →
2.11.14 C1 Yes Details →
2.11.13 C1 H1 Yes Details →
2.11.12 C1 H1 Yes Details →
2.11.11 C1 H1 Yes Details →
2.11.10 C1 H1 Yes Details →
2.11.9 C1 H1 Yes Details →
2.11.8 C1 H1 Yes Details →
2.11.7 C1 H1 Yes Details →
2.11.6 C1 H1 Yes Details →
2.11.5 C1 H1 Yes Details →
2.11.4 C1 H1 Yes Details →
2.11.3 C1 H2 Yes Details →
2.11.2 C1 H2 Yes Details →
2.11.1 C1 H2 Yes Details →
2.11.0 C1 H2 Yes Details →
2.11.RC2 C1 H2 Yes Details →
2.11.RC1 C1 H2 Yes Details →
2.10.4 C1 H2 Yes Details →
2.10.3 C1 H2 Yes Details →
2.10.2 C1 H2 Yes Details →
2.10.1 C1 H2 Yes Details →
2.10.0 C1 H2 Yes Details →
2.10.RC1 C1 H2 Yes Details →
2.10.beta1 C1 H2 Yes Details →
2.9.5 C1 H2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 1
  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for contao/core

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →

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 contao/core

Is contao/core safe to use?

Vulert records 5 vulnerabilities for contao/core in Packagist: 1 critical, 2 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does contao/core have?

5 vulnerabilities are recorded for contao/core in the Packagist ecosystem: 1 critical, 2 high, 2 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 contao/core vulnerabilities disclosed?

0 vulnerabilities were recorded for contao/core in the last 12 months, and the oldest entry in this database dates to 23 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 contao/core 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 contao/core for upcoming vulnerabilities?

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