Vulnerability Database · Packagist · Package report

juzaweb/cms: vulnerability history, versions and safety

juzaweb/cms is a package in the Packagist ecosystem. Vulert records 5 vulnerabilities for it across 70 releases, from Oct 2023 to Jun 2025. 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 H1 M2 L2
i
5 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 juzaweb/cms i

Updated on 23 Oct 2026

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

What to do: Plan around the 5 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 5 over 1 year · 0 in the last year i
  • Latest disclosure 27 Jun 2025 i
  • Highest CVSS 7.8 i
  • With no published fix 5 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 juzaweb/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
v3.4.2 M1 L2 No Details →
v3.4.1 M1 L2 No Details →
v3.4 H1 M2 L2 No Details →
v3.3.9 H1 M2 L2 No Details →
v3.3.8 H1 M2 L2 No Details →
v3.3.7 H1 M2 L2 No Details →
v3.3.6 H1 M2 L2 No Details →
v3.3.5 H1 M2 L2 No Details →
v3.3.4 H1 M2 L2 No Details →
v3.3.3 H1 M2 L2 No Details →
v3.3.2 H1 M2 L2 No Details →
v3.3.1 H1 M2 L2 No Details →
v3.3 H1 M2 L2 No Details →
v3.2.9 H1 M2 L2 No Details →
v3.2.8 H1 M2 L2 No Details →
v3.2.7 H1 M2 L2 No Details →
v3.2.6 H1 M2 L2 No Details →
v3.2.5 H1 M2 L2 No Details →
v3.2.4 H1 M2 L2 No Details →
v3.2.3 H1 M2 L2 No Details →
v3.2.2 H1 M2 L2 No Details →
v3.2.1 H1 M2 L2 No Details →
v3.2 H1 M2 L2 No Details →
v3.1.8 H1 M2 L2 No Details →
v3.1.7 H1 M2 L2 No Details →
v3.1.6 H1 M2 L2 No Details →
v3.1.5 H1 M2 L2 No Details →
v3.1.4 H1 M2 L2 No Details →
v3.1.3 H1 M2 L2 No Details →
v3.1.2 H1 M2 L2 No Details →
v3.1.1 H1 M2 L2 No Details →
v3.1.0 H1 M2 L2 No Details →
v3.0.9 H1 M2 L2 No Details →
v3.0.8 H1 M2 L2 No Details →
v3.0.7 H1 M2 L2 No Details →
v3.0.6 H1 M2 L2 No Details →
v3.0.5 H1 M2 L2 No Details →
v3.0.4 H1 M2 L2 No Details →
v3.0.3 H1 M2 L2 No Details →
v3.0.2 H1 M2 L2 No Details →
v3.0.1 H1 M2 L2 No Details →
v3.0 H1 M2 L2 No Details →
v2.0.7 H1 M2 L2 No Details →
v2.0.6 H1 M2 L2 No Details →
v2.0.5 H1 M2 L2 No Details →
v2.0.4 H1 M2 L2 No Details →
v2.0.3 H1 M2 L2 No Details →
v2.0.2 H1 M2 L2 No Details →
v2.0.1 H1 M2 L2 No Details →
v2.0 H1 M2 L2 No Details →
v1.2.5 H1 M2 L2 No Details →
v1.2.4 H1 M2 L2 No Details →
v1.1.7.3 H1 M2 L2 No Details →
v1.1.7.2 H1 M2 L2 No Details →
v1.1.7.1 H1 M2 L2 No Details →
v1.1.7 H1 M2 L2 No Details →
v1.1.6.1 H1 M2 L2 No Details →
v1.1.6 H1 M2 L2 No Details →
v1.1.5 H1 M2 L2 No Details →
v1.1.4 H1 M2 L2 No Details →
v1.1.3 H1 M2 L2 No Details →
v1.1.2 H1 M2 L2 No Details →
v1.1.1 H1 M2 L2 No Details →
v1.0.6 H1 M2 L2 No Details →
v1.0.5 H1 M2 L2 No Details →
v1.0.4 H1 M2 L2 No Details →
v1.0.3 H1 M2 L2 No Details →
v1.0.2 H1 M2 L2 No Details →
v1.0.1 H1 M2 L2 No Details →
v1.0 H1 M2 L2 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1
  • 2025 3

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 juzaweb/cms

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 juzaweb/cms

Is juzaweb/cms safe to use?

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

How many vulnerabilities does juzaweb/cms have?

5 vulnerabilities are recorded for juzaweb/cms in the Packagist ecosystem: 0 critical, 1 high, 2 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new juzaweb/cms vulnerabilities disclosed?

0 vulnerabilities were recorded for juzaweb/cms in the last 12 months, and the oldest entry in this database dates to 28 Oct 2023. 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 juzaweb/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 juzaweb/cms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the juzaweb/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.