Vulnerability in openmage/magento-lts (CVE-2026-42458)
Summary
Vulnerability in openmage/magento-lts (CVE-2026-42458). Risk of unauthorized operations or information disclosure. Exploitable via Import. Mitigation: upgrade to 20.18.0 or later.
Original description
The description as published by the source.
Magento Long Term Support (LTS) is an unofficial, community-driven project provides an alternative to the Magento Community Edition e-commerce platform with a high level of backward compatibility. Prior to 20.18.0, there is a reflected XSS vulnerability under admin panel -> System -> Import/Export -> Dataflow - Profiles. This vulnerability is fixed in 20.18.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42458 has been found in openmage/magento-lts.
Attackers can target a specific entry point like Import over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openmage/magento-lts to 20.18.0 or later.
If unsure, ask your IT team or search "openmage/magento-lts CVE-2026-42458" on the vendor's site.
CVE-2026-42458 (openmage/magento-lts) — CWE-87
Attack surface: Import
Patched: 20.18.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-87) exists in openmage/magento-lts. Attackers reach the vulnerable code path via Import.
Check the vendor advisory for the affected versions of openmage/magento-lts. Attack surface: Import.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 20.18.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openmage/magento-lts' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openmage/magento-lts' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openmage/magento-ltsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openmage/magento-lts to 20.18.0ステージング環境で 20.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com