VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

winter/wn-cms-module: vulnerability history, versions and safety

winter/wn-cms-module is a package in the Packagist ecosystem. Vulert records 3 vulnerabilities for it across 26 releases, from Dec 2024 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 12 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all winter/wn-cms-module vulnerabilities

Vulert verdict on winter/wn-cms-module i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 3 vulnerabilities on record across 1 year, 2 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 3 over 1 year · 2 in the last year i
  • Latest disclosure 12 Aug 2026 i
  • Highest CVSS 8.4 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 winter/wn-cms-module, 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
v1.2.12 M1 Yes Details →
v1.2.11 M1 Yes Details →
v1.2.10 M1 Yes Details →
v1.2.9 M1 L1 Yes Details →
v1.2.8 M1 L1 Yes Details →
v1.2.7 M1 L1 Yes Details →
v1.2.6 H1 M1 L1 Yes Details →
v1.2.5 H1 M1 L1 Yes Details →
v1.2.4 H1 M1 L1 Yes Details →
v1.2.3 H1 M1 L1 Yes Details →
v1.2.2 H1 M1 L1 Yes Details →
v1.2.1 H1 M1 L1 Yes Details →
v1.2.0 H1 M1 L1 Yes Details →
v1.1.11 M1 L1 Yes Details →
v1.1.10 M1 L1 Yes Details →
v1.1.9 M1 L1 Yes Details →
v1.1.8 M1 L1 Yes Details →
v1.1.7 M1 L1 Yes Details →
v1.1.6 M1 L1 Yes Details →
v1.1.5 M1 L1 Yes Details →
v1.1.4 M1 L1 Yes Details →
v1.1.3 M1 L1 Yes Details →
v1.1.2 M1 L1 Yes Details →
v1.0.475 M1 L1 Yes Details →
v1.0.474 M1 L1 Yes Details →
v1.0.473 M1 L1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for winter/wn-cms-module

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-54149: Winter CMS Modules Twig Sandbox Bypass Vulnerability 8.4 high 1.2.7 09 Dec 2024
CVE-2026-32639: Winter CMS - Broken Access Control in Cms\Controllers\Index Allows Unauthorized Actions 6.8 medium 1.2.13 12 Aug 2026
CVE-2026-22254: Winter CMS Asset Manager Vulnerability Leading to Stored XSS 0.0 low 1.2.10 04 Feb 2026

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 winter/wn-cms-module

Is winter/wn-cms-module safe to use?

Vulert records 3 vulnerabilities for winter/wn-cms-module in Packagist: 0 critical, 1 high, 1 medium and 1 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 winter/wn-cms-module have?

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

How often are new winter/wn-cms-module vulnerabilities disclosed?

2 vulnerabilities were recorded for winter/wn-cms-module in the last 12 months, and the oldest entry in this database dates to 09 Dec 2024. 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 winter/wn-cms-module 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 winter/wn-cms-module for upcoming vulnerabilities?

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