winter/wn-cms-module vulnerabilities

CMS module for Winter CMS

Registry
Composer
Latest
1.2.15
License
MIT

3 known advisories

The latest version, 1.2.15, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require winter/wn-cms-module:^1.2.15

Is your project on an affected winter/wn-cms-module?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for winter/wn-cms-module

  • MediumCVE-2026-32639GHSA-5c4f-9pq9-6c7712 Aug 2026

    Winter: Broken access control in `Cms\Controllers\Index` allows cross-template actions and unauthorized asset uploads

    Affected
    <1.2.13
    Fixed in
    1.2.13
  • LowCVE-2026-22254GHSA-m7gw-rffq-rxjm4 Feb 2026

    Winter CMS has Stored Cross-site Scripting (XSS) in Asset Manager

    Affected
    <1.2.10
    Fixed in
    1.2.10
  • HighCVE-2024-54149GHSA-xhw3-4j3m-hq539 Dec 2024

    Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion

    Affected
    >=1.2.0 <1.2.7 · >=1.1.0 <1.1.11 · <1.0.476
    Fixed in
    1.0.476, 1.1.11, 1.2.7

Is your winter/wn-cms-module version vulnerable?

Which of your client projects still run an old winter/wn-cms-module?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.