Vulnerability Database · Packagist · Package report

pyrocms/pyrocms: vulnerability history, versions and safety

pyrocms/pyrocms is a package in the Packagist ecosystem. Vulert records 4 vulnerabilities for it across 66 releases, from May 2022 to Aug 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 H1 M1
i
4 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 pyrocms/pyrocms i

Updated on 23 Oct 2026

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

What to do: Plan around the 4 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 4 over 1 year · 0 in the last year i
  • Latest disclosure 04 Aug 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 4 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 pyrocms/pyrocms, 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.4.11 C2 H1 M1 No Details →
3.0.0-alpha2 C2 H1 M1 No Details →
3.0.0-alpha1 C2 H1 M1 No Details →
v3.9.1 C1 No Details →
v3.9.0 C1 No Details →
v3.8.3 C2 No Details →
v3.8.2 C2 No Details →
v3.8.1 C2 No Details →
v3.8.0 C2 No Details →
v3.7.1 C2 No Details →
v3.7.0 C2 No Details →
v3.6.5 C2 H1 M1 No Details →
v3.6.4 C2 H1 M1 No Details →
v3.6.3 C2 H1 M1 No Details →
v3.6.2 C2 H1 M1 No Details →
v3.6.1 C2 H1 M1 No Details →
v3.6.0 C2 H1 M1 No Details →
v3.5.3 C2 H1 M1 No Details →
v3.5.2 C2 H1 M1 No Details →
v3.5.1 C2 H1 M1 No Details →
v3.5.0 C2 H1 M1 No Details →
v3.4.15 C2 H1 M1 No Details →
v3.4.14 C2 H1 M1 No Details →
v3.4.13 C2 H1 M1 No Details →
v3.4.12 C2 H1 M1 No Details →
v3.4.10 C2 H1 M1 No Details →
v3.4.9 C2 H1 M1 No Details →
v3.4.8 C2 H1 M1 No Details →
v3.4.7 C2 H1 M1 No Details →
v3.4.6 C2 H1 M1 No Details →
v3.4.5 C2 H1 M1 No Details →
v3.4.4 C2 H1 M1 No Details →
v3.4.3 C2 H1 M1 No Details →
v3.4.2 C2 H1 M1 No Details →
v3.4.1 C2 H1 M1 No Details →
v3.4.0 C2 H1 M1 No Details →
v3.3.9 C2 H1 M1 No Details →
v3.3.8 C2 H1 M1 No Details →
v3.3.7 C2 H1 M1 No Details →
v3.3.6 C2 H1 M1 No Details →
v3.3.5 C2 H1 M1 No Details →
v3.3.4 C2 H1 M1 No Details →
v3.3.3 C2 H1 M1 No Details →
v3.3.2 C2 H1 M1 No Details →
v3.3.1 C2 H1 M1 No Details →
v3.3.0 C2 H1 M1 No Details →
v3.2.3 C2 H1 M1 No Details →
v3.2.2 C2 H1 M1 No Details →
v3.2.1 C2 H1 M1 No Details →
v3.2.0 C2 H1 M1 No Details →
v3.1.5 C2 H1 M1 No Details →
v3.1.4 C2 H1 M1 No Details →
v3.1.3 C2 H1 M1 No Details →
v3.1.2 C2 H1 M1 No Details →
v3.1.1 C2 H1 M1 No Details →
v3.1.0 C2 H1 M1 No Details →
v3.0.2 C2 H1 M1 No Details →
v3.0.1 C2 H1 M1 No Details →
v3.0.0 C2 H1 M1 No Details →
v3.0.0-rc2 C2 H1 M1 No Details →
v3.0.0-rc1 C2 H1 M1 No Details →
v3.0.0-beta3 C2 H1 M1 No Details →
v3.0.0-beta2 C2 H1 M1 No Details →
v3.0.0-beta1 C2 H1 M1 No Details →
v2.3.0-beta1 C2 H1 M1 No Details →
v2.3.0-alpha1 C2 H1 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for pyrocms/pyrocms

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 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 pyrocms/pyrocms

Is pyrocms/pyrocms safe to use?

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

How many vulnerabilities does pyrocms/pyrocms have?

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

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

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