https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 04:22:59 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-6466 EUVD-2026-6466 https://cve.radiocsirt.org/vuln/euvd-2026-6466 https://cve.radiocsirt.org/vuln/fkie_cve-2024-41676 <p>Magento-lts is a long-term support alternative to Magento Community Edition (CE). This XSS vulnerability affects the design/header/welcome, design/header/logo_src, design/header/logo_src_small, and design/header/logo_alt system configs.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. The problem is patched with Version 20.10.1 or higher.</p> <p>Magento-lts is a long-term support alternative to Magento Community Edition (CE). This XSS vulnerability affects the design/header/welcome, design/header/logo_src, design/header/logo_src_small, and design/header/logo_alt system configs.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. The problem is patched with Version 20.10.1 or higher.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-41676 https://cve.radiocsirt.org/vuln/ghsa-5vrp-638w-p8m2 <p><strong>Affected:</strong> Packagist: openmage/magento-lts</p> <p>### Impact</p> <p>This XSS vulnerability is about the system configs * design/header/welcome * design/header/logo_src * design/header/logo_src_small * design/header/logo_alt</p> <p>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.</p> <p>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.</p> <p>### Patches _Has the problem been patched? What versions should users upgrade to?_</p> <p>The problem is patched with Version 20.10.1 or higher.</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_</p> <p>Possible mitigations are * Restricting access to the System Configs * checking templates where these settings are used to apply proper html filtering</p> <p>### For Users relying on this possibility</p> <p>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 `-&gt;getUnescapedValue()` method on this escaped elements. Developers should have a look at the newly introduced `Mage_Core_Model_Security_HtmlEscapedString`</p> <p>### Credit</p> <p>Credit goes to Aakash Adhikari @justlife4x4 for finding this issue</p> <p><strong>Affected:</strong> Packagist: openmage/magento-lts</p> <p>### Impact</p> <p>This XSS vulnerability is about the system configs * design/header/welcome * design/header/logo_src * design/header/logo_src_small * design/header/logo_alt</p> <p>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.</p> <p>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.</p> <p>### Patches _Has the problem been patched? What versions should users upgrade to?_</p> <p>The problem is patched with Version 20.10.1 or higher.</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_</p> <p>Possible mitigations are * Restricting access to the System Configs * checking templates where these settings are used to apply proper html filtering</p> <p>### For Users relying on this possibility</p> <p>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 `-&gt;getUnescapedValue()` method on this escaped elements. Developers should have a look at the newly introduced `Mage_Core_Model_Security_HtmlEscapedString`</p> <p>### Credit</p> <p>Credit goes to Aakash Adhikari @justlife4x4 for finding this issue</p> https://cve.radiocsirt.org/vuln/ghsa-5vrp-638w-p8m2