GHSA-V7CF-8GH9-GXMJ
Vulnerability from github – Published: 2026-08-12 14:40 – Updated: 2026-08-12 14:40Impact
Users with the backend.manage_branding ("Customize the back-end") permission can provide custom CSS through Settings → Customize Backend → Styles that is 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_branding permission only be granted to trusted administrators and developers.
A related issue exists in the custom styles field at Settings → Editor Settings → Markup Styles (backend.manage_editor 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.
Workarounds
Apply https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720 manually if unable to upgrade to v1.2.13.
Resources
- CVE-2025-61676 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.2.12"
},
"package": {
"ecosystem": "Packagist",
"name": "winter/wn-backend-module"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.13"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-32257"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-12T14:40:21Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Impact \n\nUsers with the `backend.manage_branding` (\"Customize the back-end\") permission can provide custom CSS through **Settings \u2192 Customize Backend \u2192 Styles** that is 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.\n\nAlthough this is a valid security issue, it\u0027s 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` permission only be granted to trusted administrators and developers.\n\nA related issue exists in the custom styles field at **Settings \u2192 Editor Settings \u2192 Markup Styles** (`backend.manage_editor` permission), which uses the same rendering mechanism and is addressed separately.\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.13.\n\n### Workarounds\n\nApply [https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720](https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720) manually if unable to upgrade to v1.2.13.\n\n### Resources\n\n- CVE-2025-61676 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)",
"id": "GHSA-v7cf-8gh9-gxmj",
"modified": "2026-08-12T14:40:21Z",
"published": "2026-08-12T14:40:21Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/security/advisories/GHSA-v7cf-8gh9-gxmj"
},
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720"
},
{
"type": "PACKAGE",
"url": "https://github.com/wintercms/winter"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Winter: Stored XSS through Brand Settings custom styles"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.