GHSA-vgp4-2fc4-qff2: XSS

Published Aug 12, 2026
·
Updated

Impact Authenticated Backend Users with the backend.manageeditor ("Manage editor settings") 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.

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.manageeditor permission only be granted to trusted administrators and developers.

A related issue exists in the custom CSS field at Settings → Customize Backend → Styles (backend.managebranding 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. The renderCss() method now applies striptags() to compiled CSS output before returning it.

Workarounds

Apply https://github.com/wintercms/winter/commit/d28f0b9474af79cfaa80eeb9d691f7a7c4469720 manually if unable to upgrade to v1.2.13.

Resources

- CVE-2025-61674 (identical vulnerability in October CMS, patched in v3.7.13 and v4.0.12)

Affected Software

1 affected componentFixes available
composer/winter/wn-backend-module>=1.2.10<1.2.13
1.2.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/winter/wn-backend-module to a version that resolves this vulnerability.

    Fixed in 1.2.13
  2. Upgrade

    Upgrade Winter CMS to a version that resolves this vulnerability.

    Fixed in 3.7.13
  3. Upgrade

    Upgrade Winter CMS to a version that resolves this vulnerability.

    Fixed in 4.0.12
  4. Upgrade

    Upgrade Winter CMS to a version that resolves this vulnerability.

    Fixed in 1.2.13Patch d28f0b9474af79cfaa80eeb9d691f7a7c4469720
  5. Configuration

    Ensure the backend.manage_editor ("Manage editor settings") permission is only granted to trusted administrators/developers because authenticated backend users with this permission can provide custom markup/styles that are compiled and rendered on every backend page.

    Winter CMS backend.manage_editor permission = grant only to trusted administrators and developers

Event History

Aug 12, 2026
Advisory Published
via GitHub·02:40 PM
Data Sourced
via GitHub·02:40 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of GHSA-vgp4-2fc4-qff2?

GHSA-vgp4-2fc4-qff2 has a high severity rating of 8.1.

2

What is the nature of the vulnerability in GHSA-vgp4-2fc4-qff2?

GHSA-vgp4-2fc4-qff2 is a cross-site scripting (XSS) vulnerability affecting backend users with specific permissions.

3

How can I mitigate the risk of GHSA-vgp4-2fc4-qff2?

To mitigate GHSA-vgp4-2fc4-qff2, restrict the 'backend.manage_editor' permission to trusted users only.

4

Does GHSA-vgp4-2fc4-qff2 affect all users?

GHSA-vgp4-2fc4-qff2 only affects authenticated backend users with the 'backend.manage_editor' permission.

5

What software is impacted by GHSA-vgp4-2fc4-qff2?

GHSA-vgp4-2fc4-qff2 affects the composer/winter/wn-backend-module software.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203