Winter CMS: Stored XSS through cached Brand Settings and Editor Settings custom styles
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| wintercms | winter | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wintercms | Winter |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5cwr-5jxg-pcf6 | Winter: Stored XSS through cached Brand Settings and Editor Settings custom styles |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.395% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wintercms
Wintercms winter |
|
| Vendors & Products |
Wintercms
Wintercms winter |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Winter CMS: Stored XSS through cached Brand Settings and Editor Settings custom styles | |
| Weaknesses | CWE-79 | |
| References |
| |
| Metrics |
cvssV3_1
|