Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.4

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

CVE-2024-54149GHSA-xhw3-4j3m-hq53

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (winter/wn-cms-module 1.2.7, 1.1.11, 1.0.476), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist winter/wn-cms-module

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.4 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
EPSS
  • CVE-2024-54149: 0.42% estimated exploitation activity in the next 30 days; percentile 36.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Affected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions. As all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous. To actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions: - cms.managelayouts - cms.managepages - cms.managepartials The Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general. Patches In order to mitigate this issue, we…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xhw3-4j3m-hq53

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-54149

Advisory: Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion
IDs: CVE-2024-54149, GHSA-xhw3-4j3m-hq53
Record: https://patchnext.com/advisories/cve-2024-54149 (revision 1, source checked 26 Oct 2026, 14:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: winter/wn-cms-module 1.2.7, 1.1.11, 1.0.476. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist winter/wn-cms-module: affected >= 1.2.0, < 1.2.7; >= 1.1.0, < 1.1.11; < 1.0.476; fixed in 1.1.11, 1.2.7, 1.0.476

## Suggested inspection (read-only)
- Packagist winter/wn-cms-module: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on winter/wn-cms-module.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xhw3-4j3m-hq53 (GitHub-reviewed advisory GHSA-xhw3-4j3m-hq53 lists affected ranges: Packagist winter/wn-cms-module >=1.2.0 =1.1.0 =0 <1.0.476)

Commands are suggestions: review each one before running it.

Loading voting…