Winter CMS XSS in cached backend CSS rendering
wintercms winter
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| winter/wn-backend-module Packagist |
|
|
Original description
Winter CMS is a content management system built on the Laravel PHP framework. Prior to 1.2.14, BrandSetting::renderCss() and EditorSetting::renderCss() store raw LESS compiler output with Cache::forever() but apply strip_tags() only to the value returned on a cache miss. The first render after saving custom CSS appears sanitized while priming an unsafe cache entry, and later cache hits return unsanitized output into the backend style element, allowing a user with backend.manage_branding or backend.manage_editor to cause stored cross-site scripting when another backend page renders the styles. The styles also appear on unauthenticated backend sign-in, password restore, and password reset layouts. This issue is fixed in version 1.2.14.
From the CVE record · GitHub_M
References
- github.com/wintercms/winter/security/advisories/GHSA-5cwr-5jxg-pcf6
- github.com/wintercms/winter/commit/c95d780ab54f3a3f74a94ae1667bf12b3c549d5d
- github.com/wintercms/winter/releases/tag/v1.2.14
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/125xxx/CVE-2026-125338.json
- nvd.nist.gov/vuln/detail/CVE-2026-125338
- github.com/wintercms/winter