Read the docs

Stored cross-site scripting in Winter CMS through cached custom styles

Priority LOW 21CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Required
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.

Summary

Winter CMS before 1.2.14 is affected. The Brand Settings and Editor Settings custom CSS are cached without sanitization, so the first render looks clean while later cache hits return unsanitized output (CWE-79). A user with backend.manage_branding or backend.manage_editor permission can store script that runs when other backend pages render the styles, including unauthenticated sign-in and password pages.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00395 34th percentileScored 2026-11-16
Fix Fixed winter (wintercms): 1.2.14

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
wintercmswinterbefore 1.2.141.2.14Patch availableCNA
  • winter Vendorwintercms Affected before 1.2.14 Fixed in 1.2.14 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:wintercms:winter:*:*:*:*:*:*:*:*——wintercms
  • cpe:2.3:a:wintercms:winter:*:*:*:*:*:*:*:* Versions — — ·wintercms

Remediation

Update winter/winter to version 1.2.14, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA winter (wintercms) Fixed in 1.2.14

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-125338
  2. 2026-11-14 CISA SSVC decision points changed

References

  • TI-2024-19497 Server-side Template Injection (SSTI) vulnerability in Winter CMS v.1.2.3 allows a remote… CVSS 3.1HIGH 7.2
  • TI-2023-28528 Winter CMS Local File Inclusion through Server Side Template Injection CVSS 3.1MEDIUM 5.4
  • TI-2022-18732 Winter vulnerable to Prototype Pollution in Snowboard framework CVSS 3.1CRITICAL 9.8
  • TI-2026-55251 Winter CMS before 1.2.13 Twig Sandbox Escape via SecurityPolicy CVSS 4.0CRITICAL 9.3
  • TI-2026-21979 Winter: Privilege escalation by authenticated backend users CVSS 3.1CRITICAL 10.0
  • TI-2024-21102 Dusk plugin may allow unfettered user authentication in misconfigured installs CVSS 3.1HIGH 8.8
See all 24 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences