GHSA-5cwr-5jxg-pcf6: Winter Cross-Site Scripting Vulnerability

MODERATE
CVSS 4.5
CWE-79
Published
Advisory Summary

GHSA-5cwr-5jxg-pcf6 is a MODERATE (CVSS 4.5) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Winter libraries in the Packagist ecosystem. The issue involves stored xss through cached brand settings and editor settings custom styles. Remediation is available by upgrading affected packages to version 1.2.14.

GHSA-5cwr-5jxg-pcf6 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5cwr-5jxg-pcf6
Severity MODERATE
CVSS v3.1 Base Score 4.5
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Winter
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-5cwr-5jxg-pcf6

To remediate this vulnerability, upgrade all affected Winter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

winter/wn-backend-module fixed: 1.2.14
Upgrade winter/wn-backend-module to 1.2.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for winter/wn-backend-module

How to Check if You Are Affected

To determine whether your application is affected by GHSA-5cwr-5jxg-pcf6, inspect your project dependencies for Winter:

inspect dependencies for winter/wn-backend-module

Analyze the terminal output to locate any version of Winter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.14), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Winter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Users with the `backend.manage_branding` ("Customize the back-end") or `backend.manage_editor` ("Manage global code editor preferences") permission can provide custom CSS through **Settings → Customize Backend → Styles** or **Settings → Editor Settings → Markup Styles** that is compiled through the LESS CSS parser and rendered on every backend page. v1.2.13 addressed CVE-2026-32257 and CVE-2026-32258 by applying `strip_tags()` to the compiled output of `BrandSetting::renderCss()` and `EditorSetting::renderCss()`. That fix was incomplete. Both methods cache the **raw** compiler output with `Cache::forever()` and applied `strip_tags()` only to the value returned on a cache miss, so every subsequent cache hit returned the unsanitized value directly into the backend `<style>` element. The first page render after saving therefore appears sanitized while priming an unsafe cache entry, and the stored XSS remains exploitable from the second render onwards. Because the custom styles partial is included by both the standard backend layout head and the backend authentication layout, an injected payload also renders on the unauthenticated backend sign-in, password restore, and password reset pages. 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` and `backend.manage_editor` permissions only be granted to trusted administrators and developers. 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.14. The `renderCss()` methods now apply `strip_tags()` to the cached value when it is read back, which also neutralizes any cache entry that was poisoned before upgrading. The `backend.manage_editor` and `backend.manage_default_dashboard` permissions have additionally been given warning comments in the permission editor, matching the existing warning on `backend.manage_branding`. ### Workarounds Apply [https://github.com/wintercms/winter/commit/c95d780ab54f3a3f74a94ae1667bf12b3c549d5d](https://github.com/wintercms/winter/commit/c95d780ab54f3a3f74a94ae1667bf12b3c549d5d) manually if unable to upgrade to v1.2.14. Clearing the application cache removes an already-poisoned entry, but it will be recreated on the next backend page render unless the patch is applied. ### References - CVE-2026-32257 / GHSA-v7cf-8gh9-gxmj (Stored XSS through Brand Settings custom styles, incompletely patched in v1.2.13) - CVE-2026-32258 / GHSA-vgp4-2fc4-qff2 (Stored XSS through Editor Settings custom styles, incompletely patched in v1.2.13) - CVE-2025-61674 and CVE-2025-61676 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)

GHSA-5cwr-5jxg-pcf6 Affected Winter Versions

1 component(s)
Fixed Versions:
1.2.14
Product / Package Ecosystem Affected Versions Fixed Version
winter/wn-backend-module
Packagist
< 1.2.14
1.2.14

References

Frequently Asked Questions

What is GHSA-5cwr-5jxg-pcf6?
GHSA-5cwr-5jxg-pcf6 is a security vulnerability in Winter involving Stored XSS through cached Brand Settings and Editor Settings custom styles under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Winter versions are affected?
Affected versions include releases prior to 1.2.14 across affected packages: winter/wn-backend-module.
What version fixes GHSA-5cwr-5jxg-pcf6?
Upgrading to 1.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is winter/wn-backend-module affected?
Yes, winter/wn-backend-module is affected in releases prior to 1.2.14. Upgrade your dependency to 1.2.14 or later.
What is the CVSS score of GHSA-5cwr-5jxg-pcf6?
GHSA-5cwr-5jxg-pcf6 has a CVSS v3.1 base score of 4.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N.
What CWE is associated with GHSA-5cwr-5jxg-pcf6?
GHSA-5cwr-5jxg-pcf6 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for GHSA-5cwr-5jxg-pcf6?
Run the dependency tree command: 'inspect dependencies for winter/wn-backend-module'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5cwr-5jxg-pcf6",
  "modified" : "2026-08-20T18:44:54Z",
  "published" : "2026-08-20T18:44:54Z",
  "aliases" : [ ],
  "summary" : "Winter: Stored XSS through cached Brand Settings and Editor Settings custom styles",
  "details" : "### Impact\n\nUsers with the `backend.manage_branding` (\"Customize the back-end\") or `backend.manage_editor` (\"Manage global code editor preferences\") permission can provide custom CSS through **Settings → Customize Backend → Styles** or **Settings → Editor Settings → Markup Styles** that is compiled through the LESS CSS parser and rendered on every backend page.\n\nv1.2.13 addressed CVE-2026-32257 and CVE-2026-32258 by applying `strip_tags()` to the compiled output of `BrandSetting::renderCss()` and `EditorSetting::renderCss()`. That fix was incomplete. Both methods cache the **raw** compiler output with `Cache::forever()` and applied `strip_tags()` only to the value returned on a cache miss, so every subsequent cache hit returned the unsanitized value directly into the backend `<style>` element. The first page render after saving therefore appears sanitized while priming an unsafe cache entry, and the stored XSS remains exploitable from the second render onwards.\n\nBecause the custom styles partial is included by both the standard backend layout head and the backend authentication layout, an injected payload also renders on the unauthenticated backend sign-in, password restore, and password reset pages.\n\nAlthough 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` and `backend.manage_editor` permissions only be granted to trusted administrators and developers.\n\nAll users are advised to update to the latest version to ensure their systems remain secure.\n\n### Patches\n\nThis issue has been patched in v1.2.14. The `renderCss()` methods now apply `strip_tags()` to the cached value when it is read back, which also neutralizes any cache entry that was poisoned before upgrading.\n\nThe `backend.manage_editor` and `backend.manage_default_dashboard` permissions have additionally been given warning comments in the permission editor, matching the existing warning on `backend.manage_branding`.\n\n### Workarounds\n\nApply [https://github.com/wintercms/winter/commit/c95d780ab54f3a3f74a94ae1667bf12b3c549d5d](https://github.com/wintercms/winter/commit/c95d780ab54f3a3f74a94ae1667bf12b3c549d5d) manually if unable to upgrade to v1.2.14.\n\nClearing the application cache removes an already-poisoned entry, but it will be recreated on the next backend page render unless the patch is applied.\n\n### References\n\n- CVE-2026-32257 / GHSA-v7cf-8gh9-gxmj (Stored XSS through Brand Settings custom styles, incompletely patched in v1.2.13)\n- CVE-2026-32258 / GHSA-vgp4-2fc4-qff2 (Stored XSS through Editor Settings custom styles, incompletely patched in v1.2.13)\n- CVE-2025-61674 and CVE-2025-61676 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "winter/wn-backend-module"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.14"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.2.13"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/security/advisories/GHSA-5cwr-5jxg-pcf6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/commit/c95d780ab54f3a3f74a94ae1667bf12b3c549d5d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/wintercms/winter"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/releases/tag/v1.2.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T18:44:54Z",
    "nvd_published_at" : null
  }
}