CVE-2024-41676

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

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-41676 has a CVSS score of 4.1 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (20.10.1); upgrading removes the vulnerable code path.

Kodem intelligence

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

The problem is patched with Version 20.10.1 or higher.

1. What is CVE-2024-41676? CVE-2024-41676 is a medium-severity cross-site scripting (XSS) vulnerability in openmage/magento-lts (composer), affecting versions < 20.10.1. It is fixed in 20.10.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-41676? CVE-2024-41676 has a CVSS score of 4.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openmage/magento-lts are affected by CVE-2024-41676? openmage/magento-lts (composer) versions < 20.10.1 is affected.
4. Is there a fix for CVE-2024-41676? Yes. CVE-2024-41676 is fixed in 20.10.1. Upgrade to this version or later.
5. Is CVE-2024-41676 exploitable, and should I be worried? Whether CVE-2024-41676 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-41676 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-41676? Upgrade openmage/magento-lts to 20.10.1 or later.