Vulnerability advisory

GHSA-5vrp-638w-p8m2

Magento LTS vulnerable to stored Cross-site Scripting (XSS) in admin system configs

Published Jul 29, 2024Updated Sep 10, 2026OSV record ↗

Also known as CVE-2024-41676

Severity

CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N
CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

Affected versions

openmage/magento-lts Packagist

All openmage/magento-lts advisories →

Affected Fixed in

All versions before 20.10.1 20.10.1Advisories →

Affected	Fixed in
All versions before 20.10.1	`20.10.1`Advisories →
Also listed as affected (79) `1.9.1.1` `1.9.2.0` `1.9.2.1` `1.9.2.2` `1.9.2.3` `1.9.2.4` `1.9.3.0` `1.9.3.1` `v19.4.0` `v19.4.1` `v19.4.10` `v19.4.11` `v19.4.12` `v19.4.13` `v19.4.14` `v19.4.15` `v19.4.16` `v19.4.17` `v19.4.18` `v19.4.19` `v19.4.2` `v19.4.20` `v19.4.21` `v19.4.22` `v19.4.23` `v19.4.3` `v19.4.4` `v19.4.5` `v19.4.6` `v19.4.7` `v19.4.8` `v19.4.9` `v19.5.0` `v19.5.0-rc1` `v19.5.0-rc2` `v19.5.0-rc3` `v19.5.0-rc4` `v19.5.0-rc5` `v19.5.1` `v19.5.2` `v19.5.3` `v20.0.0` `v20.0.1` `v20.0.10` `v20.0.11` `v20.0.12` `v20.0.13` `v20.0.14` `v20.0.15` `v20.0.16` `v20.0.17` `v20.0.18` `v20.0.19` `v20.0.2` `v20.0.20` `v20.0.3` `v20.0.4` `v20.0.5` `v20.0.6` `v20.0.7` `v20.0.8` `v20.1.0` `v20.1.0-rc1` `v20.1.0-rc2` `v20.1.0-rc3` `v20.1.0-rc4` `v20.1.0-rc5` `v20.1.0-rc6` `v20.1.0-rc7` `v20.1.1` `v20.10.0` `v20.2.0` `v20.3.0` `v20.4.0` `v20.5.0` `v20.6.0` `v20.7.0` `v20.8.0` `v20.9.0`

Also listed as affected (79)

Description

Impact

This XSS vulnerability is about the system configs

design/header/welcome
design/header/logo_src
design/header/logo_src_small
design/header/logo_alt

They are intended to enable admins to set a text in the two cases, and to define an image url for the other two cases. But because of previously missing escaping allowed to input arbitrary html and as a consequence also arbitrary JavaScript.

While this is in most usage scenarios not a relevant issue, some people work with more restrictive roles in the backend. Here the ability to inject JavaScript with these settings would be an unintended and unwanted privilege.

Patches

Has the problem been patched? What versions should users upgrade to?

The problem is patched with Version 20.10.1 or higher.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Possible mitigations are

Restricting access to the System Configs
checking templates where these settings are used to apply proper html filtering

For Users relying on this possibility

Some Users might actually rely on the ability to use html there. You can restore the previous behavior by making use of the new introduced ->getUnescapedValue() method on this escaped elements. Developers should have a look at the newly introduced Mage_Core_Model_Security_HtmlEscapedString

Credit

Credit goes to Aakash Adhikari @justlife4x4 for finding this issue