https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 13:19:15 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-32258 <p>Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. From 1.2.10 through 1.2.12, authenticated backend users with the backend.manage_editor permission can store custom Markup Styles that are compiled by the LESS parser and rendered without sanitization on every backend page, allowing stored cross-site scripting. This issue is fixed in version 1.2.13.</p> <p>Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. From 1.2.10 through 1.2.12, authenticated backend users with the backend.manage_editor permission can store custom Markup Styles that are compiled by the LESS parser and rendered without sanitization on every backend page, allowing stored cross-site scripting. This issue is fixed in version 1.2.13.</p> https://db.gcve.eu/vuln/fkie_cve-2026-32258 https://db.gcve.eu/vuln/ghsa-vgp4-2fc4-qff2 <p><strong>Affected:</strong> Packagist: winter/wn-backend-module</p> <p>### Impact Authenticated Backend Users with the `backend.manage_editor` (&#34;Manage editor settings&#34;) permission can provide custom styles through **Settings → Editor Settings → Markup Styles** that are 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.</p> <p>Although this is a valid security issue, it&#39;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_editor` permission only be granted to trusted administrators and developers.</p> <p>A related issue exists in the custom CSS field at **Settings → Customize Backend → Styles** (`backend.manage_branding` permission), which uses the same rendering mechanism and is addressed separately.</p> <p>All users are advised to update to the latest version to ensure their systems remain secure.</p> <p>### Patches</p> <p>This issue has been patched in v1.2.13. The `renderCss()` method now applies `strip_tags()` to compiled CSS output before returning it.</p> <p>### Workarounds</p> <p>Apply [https://github.com/wintercms/w…</p> <p><strong>Affected:</strong> Packagist: winter/wn-backend-module</p> <p>### Impact Authenticated Backend Users with the `backend.manage_editor` (&#34;Manage editor settings&#34;) permission can provide custom styles through **Settings → Editor Settings → Markup Styles** that are 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.</p> <p>Although this is a valid security issue, it&#39;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_editor` permission only be granted to trusted administrators and developers.</p> <p>A related issue exists in the custom CSS field at **Settings → Customize Backend → Styles** (`backend.manage_branding` permission), which uses the same rendering mechanism and is addressed separately.</p> <p>All users are advised to update to the latest version to ensure their systems remain secure.</p> <p>### Patches</p> <p>This issue has been patched in v1.2.13. The `renderCss()` method now applies `strip_tags()` to compiled CSS output before returning it.</p> <p>### Workarounds</p> <p>Apply [https://github.com/wintercms/w…</p> https://db.gcve.eu/vuln/ghsa-vgp4-2fc4-qff2