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
Sanineng Reporter
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 thecolorpickerformwidget, 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