← Back
CVE-2026-42207
medium
CVSS 6.1
Open Redirect in openmage/magento-lts (CVE-2026-42207)
Summary
vulnerability in openmage/magento-lts (CVE-2026-42207). Risk of unauthorized operations or information disclosure. Exploitable via `GET /productalert/add/stock/`. Mitigation: upgrade to `20.18.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42207** has been found in openmage/magento-lts.
Attackers can target a specific entry point like `GET /productalert/add/stock/` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
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-42207" on the vendor's site.
CVE-2026-42207 (openmage/magento-lts) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /productalert/add/stock/ / `product_id` / `uenc`
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.
❓ What is the problem
**A vulnerability** (CWE-601) exists in openmage/magento-lts. Attackers reach the vulnerable code path via `GET /productalert/add/stock/` without authentication.
📍 Affected scope
openmage/magento-lts — . Attack surface: GET /productalert/add/stock/ / `product_id` / `uenc`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **20.18.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /productalert/add/stock/` requests with malformed payloads or SQL meta-characters. Run `grep -r 'openmage/magento-lts' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /productalert/add/stock/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /productalert/add/stock/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade openmage/magento-lts to 20.18.0ステージング環境で 20.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /productalert/add/stock/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
openmage/magento-lts
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.18.0"}]}]
Packagist
openmage/magento-lts
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.18.0"}]}]