Open Redirect in Movary (CVE-2025-64116)
Summary
Vulnerability in Movary (CVE-2025-64116). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.69.0 or later.
Original description
The description as published by the source.
Movary is a web application to track, rate and explore your movie watch history. Prior to 0.69.0, the login page accepts a redirect parameter without validation, allowing attackers to redirect authenticated users to arbitrary external sites. This vulnerability is fixed in 0.69.0.
Source: NIST National Vulnerability Database NVD
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-2025-64116 has been found in Movary.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade Movary to 0.69.0 or later.
If unsure, ask your IT team or search "Movary CVE-2025-64116" on the vendor's site.
CVE-2025-64116 (Movary) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.69.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-601) exists in Movary.
Check the vendor advisory for the affected versions of Movary.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 0.69.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 'Movary' . 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 'Movary' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Movaryを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Movary to 0.69.0ステージング環境で 0.69.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit github.com
- issue security-advisories@github.com
- patch security-advisories@github.com