https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T05:14:16.972032+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-6466 EUVD-2026-6466 2026-10-06T05:14:16.975895+00:00 EUVD-2026-6466 https://cve.radiocsirt.org/vuln/fkie_cve-2024-41676 fkie_cve-2024-41676 2026-10-06T05:14:16.975939+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-5vrp-638w-p8m2 GHSA-5vrp-638w-p8m2 — Magento LTS vulnerable to stored Cross-site Scripting (XSS) in admin system configs 2026-10-06T05:14:16.975988+00:00

Affected: Packagist: openmage/magento-lts

### 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