VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

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

winter/wn-backend-module is a package in the Packagist ecosystem. Vulert records 15 vulnerabilities for it across 28 releases, from Dec 2023 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
15 vulnerabilities recorded C1 H3 M8 L3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
13 in the last 12 months

Most recent disclosure 20 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all winter/wn-backend-module vulnerabilities

Vulert verdict on winter/wn-backend-module i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 15 vulnerabilities on record across 2 years, 13 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 15 over 2 years · 13 in the last year i
  • Latest disclosure 20 Aug 2026 i
  • Highest CVSS 9.9 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-backend-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
1.2.13 M1 Yes Details →
v1.2.13 M5 L1 Yes Details →
v1.2.12 H3 M7 L1 Yes Details →
v1.2.11 C1 H3 M7 L1 Yes Details →
v1.2.10 C1 H3 M7 L1 Yes Details →
v1.2.9 C1 H2 M7 L1 Yes Details →
v1.2.8 C1 H2 M7 L1 Yes Details →
v1.2.7 C1 H2 M7 L1 Yes Details →
v1.2.6 C1 H2 M7 L1 Yes Details →
v1.2.5 C1 H2 M7 L1 Yes Details →
v1.2.4 C1 H2 M7 L1 Yes Details →
v1.2.3 C1 H2 M7 L3 Yes Details →
v1.2.2 C1 H2 M7 L3 Yes Details →
v1.2.1 C1 H2 M7 L3 Yes Details →
v1.2.0 C1 H2 M7 L3 Yes Details →
v1.1.11 H2 M7 L1 Yes Details →
v1.1.10 H2 M7 L1 Yes Details →
v1.1.9 H2 M7 L3 Yes Details →
v1.1.8 H2 M7 L3 Yes Details →
v1.1.7 H2 M7 L3 Yes Details →
v1.1.6 H2 M7 L3 Yes Details →
v1.1.5 H2 M7 L3 Yes Details →
v1.1.4 H2 M7 L3 Yes Details →
v1.1.3 H2 M7 L3 Yes Details →
v1.1.2 H2 M7 L3 Yes Details →
v1.0.475 H2 M7 L2 Yes Details →
v1.0.474 H2 M7 L2 Yes Details →
v1.0.473 H2 M7 L2 Yes Details →

Newest 28 of 28 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
  • 2026 13

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

03 Vulnerabilities

Recorded vulnerabilities for winter/wn-backend-module

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27591: Winter CMS Backend Module Privilege Escalation Vulnerability 9.9 critical 1.2.12 12 Mar 2026
CVE-2026-32258: Winter Backend Module Stored XSS Vulnerability 8.1 high 1.2.13 12 Aug 2026
CVE-2026-32257: Winter Backend Module Stored XSS Vulnerability 8.1 high 1.2.13 12 Aug 2026
CVE-2026-35445: Winter CMS Authenticated User Permission Bypass Vulnerability 7.1 high 1.2.13 12 Aug 2026
CSRF Vulnerability in Winter CMS Backend Module: Exploitable AJAX Handlers 6.1 medium 1.2.14 20 Aug 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-backend-module

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

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

15 vulnerabilities are recorded for winter/wn-backend-module in the Packagist ecosystem: 1 critical, 3 high, 8 medium and 3 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-backend-module vulnerabilities disclosed?

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

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