GHSA-v7cf-8gh9-gxmj
Winter: Stored XSS through Brand Settings custom styles
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Packagist | winter/wn-backend-module | < 1.2.13 | 1.2.13 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
Users with the `backend.manage_branding` ("Customize the back-end") permission can provide custom CSS through **Settings → Customize Backend → Styles** that is compiled through the LESS CSS parser and rendered on every backend page. Previously, the compiled output was not sanitized, which could have allowed a stored XSS attack.
Although this is a valid security issue, it's important to note that its severity is relatively low. To exploit the vulnerability, an attacker would already need to have trusted access to the Winter CMS backend with a specific administrative permission. The Winter CMS maintainers recommend that the `backend.manage_branding` permission only be granted to trusted administrators and developers.
A related issue exists in the custom styles field at **Settings → Editor Settings → Markup Styles** (`backend.manage_editor` permission), which uses the same rendering mechanism and is addressed separately.
All users are advised to update to the latest version to ensure their systems remain secure.
### Patches
This issue has been patched in v1.2.13.
### Workarounds
Apply [https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720](https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720) manually if unable to upgrade to v1.2.13.
### Resources
- CVE-2025-61676 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)
References
External links from the advisory. They lead to third-party sites.