Winter: Stored XSS through Editor Settings custom styles
Published 12 Aug 2026 · Updated 12 Aug 2026
Is your project on an affected winter/wn-backend-module?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=1.2.10 <1.2.13
- Fixed in
- 1.2.13
composer require winter/wn-backend-module:^1.2.13Details
Impact
Authenticated Backend Users with the backend.manage_editor ("Manage editor settings") permission can provide custom styles through Settings → Editor Settings → Markup Styles that are 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_editor permission only be granted to trusted administrators and developers.
A related issue exists in the custom CSS field at Settings → Customize Backend → Styles (backend.manage_branding 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. The renderCss() method now applies strip_tags() to compiled CSS output before returning it.
Workarounds
Apply https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720 manually if unable to upgrade to v1.2.13.
Resources
- CVE-2025-61674 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)
Is GHSA-vgp4-2fc4-qff2 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected winter/wn-backend-module, and gives you the command that fixes it.
More advisories for winter/wn-backend-module
- MediumCVE-2026-125340Winter: Reflected XSS through the search query parameter in the backend Table widget · 20 Aug 2026
- MediumCVE-2026-125339Winter: CSRF through AJAX handler names reachable as backend page actions · 20 Aug 2026
- MediumCVE-2026-125338Winter: Stored XSS through cached Brand Settings and Editor Settings custom styles · 20 Aug 2026
- HighCVE-2026-125337Winter: ImportExportController AJAX handlers bypass granular import/export permission gate · 20 Aug 2026
- MediumCVE-2026-126061Winter: My Account preview exposes another backend user's profile by record ID · 20 Aug 2026
- LowCVE-2026-125341Winter: Stored XSS through Backend List widget image columns · 20 Aug 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.