Vulnerability Database · Packagist · Package report

baserproject/basercms: vulnerability history, versions and safety

baserproject/basercms is a package in the Packagist ecosystem. Vulert records 56 vulnerabilities for it across 120 releases, from Aug 2020 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
56 vulnerabilities recorded C7 H15 M29 L5
i
7 with no fix published

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

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

Most recent disclosure 31 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on baserproject/basercms i

Updated on 23 Oct 2026

Careful: 7 of the 56 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 56 vulnerabilities on record across 5 years, 9 in the last year.

What to do: Plan around the 7 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 56 over 5 years · 9 in the last year i
  • Latest disclosure 31 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 7 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 baserproject/basercms, 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
5.2.2 C3 H3 M3 Yes Details →
5.2.1 C3 H3 M3 Yes Details →
5.2.0 C3 H3 M3 Yes Details →
5.1.10 C3 H3 M3 Yes Details →
5.1.9 C3 H3 M3 Yes Details →
5.1.8 C3 H3 M3 Yes Details →
5.1.7 C3 H3 M3 Yes Details →
5.1.6 C3 H3 M3 Yes Details →
5.1.5 C3 H3 M3 Yes Details →
5.1.4 C3 H3 M3 Yes Details →
5.1.3 C3 H3 M3 Yes Details →
5.1.2 C3 H3 M3 Yes Details →
5.1.1 C3 H3 M7 Yes Details →
5.1.0 C3 H3 M7 Yes Details →
5.0.21 C3 H3 M7 Yes Details →
5.0.20 C3 H3 M7 Yes Details →
5.0.19 C3 H3 M7 Yes Details →
5.0.18 C3 H3 M7 Yes Details →
5.0.17 C3 H3 M7 Yes Details →
5.0.16 C3 H3 M7 Yes Details →
5.0.15 C3 H3 M7 Yes Details →
5.0.14 C3 H3 M7 Yes Details →
5.0.12 C3 H3 M7 Yes Details →
5.0.11 C3 H3 M7 Yes Details →
5.0.10 C3 H3 M7 Yes Details →
5.0.9 C3 H3 M7 Yes Details →
5.0.8 C3 H3 M10 Yes Details →
5.0.7 C3 H3 M10 Yes Details →
5.0.6 C3 H3 M10 Yes Details →
5.0.5 C3 H3 M10 Yes Details →
5.0.4 C3 H3 M10 Yes Details →
5.0.3 C3 H3 M10 Yes Details →
5.0.2 C3 H3 M10 Yes Details →
5.0.1 C3 H3 M10 Yes Details →
5.0.0 C3 H3 M10 Yes Details →
5.0.0-beta4 C3 H3 M10 Yes Details →
5.0.0-beta3 C3 H3 M10 Yes Details →
5.0.0-beta2 C3 H3 M10 Yes Details →
5.0.0-beta1 C3 H3 M10 Yes Details →
4.8.2 C3 H3 M8 Yes Details →
4.8.1 C3 H3 M8 Yes Details →
4.8.0 C3 H3 M8 Yes Details →
4.7.8 C3 H3 M8 Yes Details →
4.7.7 C3 H3 M8 Yes Details →
4.7.6 C3 H3 M8 Yes Details →
4.7.5 C3 H3 M8 Yes Details →
4.7.3 C3 H3 M8 Yes Details →
4.7.2 C3 H3 M8 Yes Details →
4.7.0 C3 H3 M8 Yes Details →
4.6.3 C3 H3 M8 Yes Details →
4.6.2 C3 H3 M8 Yes Details →
4.6.1.1 C3 H3 M8 Yes Details →
4.6.1 C3 H3 M8 Yes Details →
4.6.0 C3 H3 M8 Yes Details →
4.5.6 C3 H3 M8 Yes Details →
4.5.5 C3 H3 M8 Yes Details →
4.5.4 C3 H3 M11 Yes Details →
4.5.3 C3 H3 M8 Yes Details →
4.5.2 C3 H3 M8 Yes Details →
4.5.1 C3 H3 M8 Yes Details →
4.5.0 C3 H3 M8 Yes Details →
4.4.8 C3 H3 M11 Yes Details →
4.4.7 C3 H3 M8 Yes Details →
4.4.6 C3 H3 M8 Yes Details →
4.4.5 C3 H3 M8 Yes Details →
4.4.4 C3 H3 M8 Yes Details →
4.4.3 C3 H3 M8 Yes Details →
4.4.2.1 C3 H3 M8 Yes Details →
4.4.2 C3 H3 M8 Yes Details →
4.4.1.1 C3 H3 M8 Yes Details →
4.4.1 C3 H3 M8 Yes Details →
4.4.0 C3 H3 M8 Yes Details →
4.3.7.1 C3 H3 M8 Yes Details →
4.3.7 C3 H3 M8 Yes Details →
4.3.6 C3 H3 M8 Yes Details →
4.3.5 C3 H3 M8 Yes Details →
4.3.4 C3 H3 M8 Yes Details →
4.3.3 C3 H3 M8 Yes Details →
4.3.2 C3 H3 M8 Yes Details →
4.3.1 C3 H3 M8 Yes Details →
4.3.0 C3 H3 M8 Yes Details →
4.2.5 C3 H4 M16 Yes Details →
4.2.4 C3 H4 M16 Yes Details →
4.2.3 C3 H4 M16 Yes Details →
4.2.2 C3 H4 M16 Yes Details →
4.2.1 C3 H4 M16 Yes Details →
4.2.0 C3 H4 M16 Yes Details →
4.1.8 C3 H3 M8 Yes Details →
4.1.7 C3 H3 M8 Yes Details →
4.1.6 C3 H3 M8 Yes Details →
4.1.5 C3 H3 M8 Yes Details →
4.1.4 C3 H3 M8 Yes Details →
4.1.3 C3 H3 M8 Yes Details →
4.1.2 C3 H3 M8 Yes Details →
4.1.1 C3 H3 M8 Yes Details →
4.1.0.1 C3 H4 M8 Yes Details →
4.1.0 C3 H7 M21 No Details →
4.0.11 C3 H4 M8 Yes Details →
4.0.10.1 C3 H4 M8 Yes Details →
4.0.10 C3 H4 M8 Yes Details →
4.0.9 C3 H4 M8 Yes Details →
4.0.8 C3 H4 M8 Yes Details →
4.0.7 C3 H4 M8 Yes Details →
4.0.6 C3 H4 M8 Yes Details →
4.0.5.2 C3 H4 M8 Yes Details →
4.0.5.1 C3 H4 M8 Yes Details →
4.0.5 C3 H4 M8 Yes Details →
4.0.4 C3 H4 M8 Yes Details →
4.0.3 C3 H4 M8 Yes Details →
4.0.2.1 C3 H4 M8 Yes Details →
4.0.2 C3 H4 M8 Yes Details →
4.0.1 C3 H4 M8 Yes Details →
4.0.0 C3 H7 M21 No Details →
4.0.0-beta C3 H3 M8 Yes Details →
3.0.26 C3 H5 M17 Yes Details →
3.0.25 C3 H5 M17 Yes Details →
3.0.24 C3 H5 M17 Yes Details →
3.0.23 C3 H5 M17 Yes Details →
3.0.22 C3 H5 M17 Yes Details →
3.0.21 C3 H5 M17 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 6
  • 2021 6
  • 2022 21
  • 2023 7
  • 2024 7
  • 2026 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 9 of the 56 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 baserproject/basercms

Is baserproject/basercms safe to use?

Vulert records 56 vulnerabilities for baserproject/basercms in Packagist: 7 critical, 15 high, 29 medium and 5 low. 7 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does baserproject/basercms have?

56 vulnerabilities are recorded for baserproject/basercms in the Packagist ecosystem: 7 critical, 15 high, 29 medium and 5 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new baserproject/basercms vulnerabilities disclosed?

9 vulnerabilities were recorded for baserproject/basercms in the last 12 months, and the oldest entry in this database dates to 28 Aug 2020. 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 baserproject/basercms 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 baserproject/basercms for upcoming vulnerabilities?

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