Vulnerability Database · Packagist · Package report

feehi/cms: vulnerability history, versions and safety

feehi/cms is a package in the Packagist ecosystem. Vulert records 21 vulnerabilities for it across 40 releases, from Jun 2021 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded C4 H3 M14
i
16 with no fix published

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

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

Most recent disclosure 06 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on feehi/cms i

Updated on 23 Oct 2026

Careful: 16 of the 21 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 21 vulnerabilities on record across 4 years, 7 in the last year.

What to do: Plan around the 16 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 21 over 4 years · 7 in the last year i
  • Latest disclosure 06 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 16 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 feehi/cms, 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
2.1.1 C1 H1 M13 No Details →
2.1.0.2 C1 H1 M7 No Details →
2.1.0.1 C1 H1 M7 No Details →
2.1.0 C1 H1 M7 No Details →
2.1.0-beta2 C1 H1 M7 No Details →
2.1.0-beta C1 H2 M7 No Details →
2.0.8.1 C1 H2 M7 No Details →
2.0.8 C4 H3 M8 No Details →
2.0.7.1 C4 H3 M8 No Details →
2.0.7 C4 H3 M8 No Details →
2.0.6 C4 H3 M8 No Details →
2.0.5.1 C4 H3 M8 No Details →
2.0.5 C4 H3 M8 No Details →
2.0.4.1 C4 H3 M8 No Details →
2.0.4 C4 H3 M8 No Details →
2.0.3 C4 H3 M8 No Details →
2.0.2 C4 H3 M8 No Details →
2.0.1 C4 H3 M8 No Details →
2.0.0 C4 H3 M8 No Details →
1.0.0rc2 C4 H3 M8 No Details →
1.0.0rc1 C4 H3 M8 No Details →
1.0.0beta3 C4 H3 M8 No Details →
1.0.0beta2 C4 H3 M8 No Details →
1.0.0beta1 C4 H3 M8 No Details →
1.0.0-alpha3 C4 H3 M8 No Details →
1.0.0alpha2 C4 H3 M8 No Details →
1.0.0alpha1 C4 H3 M8 No Details →
0.1.3 C4 H3 M8 No Details →
0.1.2 C4 H3 M8 No Details →
0.1.1 C4 H3 M8 No Details →
0.1.0 C4 H3 M8 No Details →
0.0.9 C4 H3 M8 No Details →
0.0.8 C4 H3 M8 No Details →
0.0.7 C4 H3 M8 No Details →
0.0.6 C4 H3 M8 No Details →
0.0.5 C4 H3 M8 No Details →
0.0.4 C4 H3 M8 No Details →
0.0.3 C4 H3 M8 No Details →
0.0.2 C4 H3 M8 No Details →
0.0.1 C4 H3 M8 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 7
  • 2023 2
  • 2024 3
  • 2025 1
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for feehi/cms

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 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 feehi/cms

Is feehi/cms safe to use?

Vulert records 21 vulnerabilities for feehi/cms in Packagist: 4 critical, 3 high, 14 medium and 0 low. 16 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does feehi/cms have?

21 vulnerabilities are recorded for feehi/cms in the Packagist ecosystem: 4 critical, 3 high, 14 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 feehi/cms vulnerabilities disclosed?

7 vulnerabilities were recorded for feehi/cms in the last 12 months, and the oldest entry in this database dates to 08 Jun 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 feehi/cms 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 feehi/cms for upcoming vulnerabilities?

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