Cross-Site Scripting (XSS) in migration-planner (CVE-2026-53472)
Summary
Cross-site scripting in migration-planner (CVE-2026-53472). Confidential information can be exposed externally. Exploitable via AgentStatusUpdate.CredentialUrl.
Original description
The description as published by the source.
A flaw was found in migration-planner. Insufficient validation of the AgentStatusUpdate.CredentialUrl field allows an authenticated attacker to store a malicious javascript: URL. When a victim views this URL in the Hybrid Cloud Console, it can lead to Cross-Site Scripting (XSS), enabling script execution in the victim's session and potentially disclosing sensitive information.
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-53472 has been found in migration-planner.
Attackers can target a specific entry point like AgentStatusUpdate.CredentialUrl over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "migration-planner CVE-2026-53472" on the vendor's site.
CVE-2026-53472 (migration-planner) — CWE-79 / CVSS v3 6.3
Attack vector: remote (network-reachable)
Attack surface: AgentStatusUpdate.CredentialUrl
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.
Cross-site scripting (XSS) (CWE-79) exists in migration-planner. Attackers reach the vulnerable code path via AgentStatusUpdate.CredentialUrl.
Check the vendor advisory for the affected versions of migration-planner. Attack surface: AgentStatusUpdate.CredentialUrl.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
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 'migration-planner' . 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 'migration-planner' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
migration-plannerを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory access.redhat.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report bugzilla.redhat.com
- web github.com