Skip to content

Winter CMS Stored XSS through Backend ColorPicker FormWidget

Low severity GitHub Reviewed Published Dec 28, 2023 in wintercms/winter • Updated Jan 2, 2024

Package

composer winter/wn-backend-module (Composer)

Affected versions

< 1.2.4

Patched versions

1.2.4

Description

Impact

Users with access to backend forms that include a ColorPicker FormWidget can provide a value that would then be rendered unescaped in the backend form, potentially allowing for a stored XSS attack.

By default, only the Brand Settings (backend.manage_branding) and Mail Brand Settings (system.manage_mail_templates) forms include the colorpicker formwidget, however it is also common for theme's to include it on their Theme Customization (cms.manage_theme_options) form.

Although this was a 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 and they would then need to convince a user with higher privileges than them to visit an affected Form in the backend.

These two factors limit the potential harm of this vulnerability. That being said, all users are advised to update to the latest version (1.2.4) to ensure their systems remain secure.

Patches

This issue has been patched in v1.2.4.

Workarounds

Apply wintercms/winter@517f65d manually if unable to upgrade to v1.2.4.

References

@LukeTowers LukeTowers published to wintercms/winter Dec 28, 2023
Published to the GitHub Advisory Database Dec 28, 2023
Reviewed Dec 28, 2023
Published by the National Vulnerability Database Dec 28, 2023
Last updated Jan 2, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.045%
(15th percentile)

Weaknesses

CVE ID

CVE-2023-52084

GHSA ID

GHSA-43w4-4j3c-jx29

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.