# CVE-2025-64116: Movary vulnerable to an open redirect

> Attackers can redirect authenticated users to malicious external sites via an unvalidated login redirect parameter in Movary.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 31 Oct 2025
- **Also known as:** GHSA-7q72-x26x-7f8g

## What is CVE-2025-64116?

CVE-2025-64116 is a medium-severity vulnerability in leepeuker movary, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-64116?

It affects 1 product.


Products: Leepeuker Movary.

## How do I fix CVE-2025-64116?

No fix has been published for CVE-2025-64116 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-64116 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64116 exists.

## Other vulnerabilities in leepeuker movary

- [CVE-2026-23839](https://insights.sbomify.com/CVE-2026-23839/): Movary vulnerable to Cross-site Scripting with `?categoryUpdated=` param (critical 9.3)
- [CVE-2026-23840](https://insights.sbomify.com/CVE-2026-23840/): Movary vulnerable to Cross-site Scripting with `?categoryDeleted=` param (critical 9.3)
- [CVE-2026-23841](https://insights.sbomify.com/CVE-2026-23841/): Movary vulnerable to Cross-site Scripting with `?categoryCreated=` param (critical 9.3)
- [CVE-2026-40349](https://insights.sbomify.com/CVE-2026-40349/): Authenticated Movary User Can Self-Escalate to Administrator via PUT /settings/users/{userId} by Setting isAdmin=true (high 8.8)
- [CVE-2026-40350](https://insights.sbomify.com/CVE-2026-40350/): Missing authorization in movary (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64116 and fix it if it is affected.

What it is: CVE-2025-64116 is a medium-severity vulnerability in leepeuker movary, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64116 exists.

Affected product: leepeuker movary. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64116/ (Markdown: https://insights.sbomify.com/CVE-2025-64116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64116
- OSV: https://osv.dev/vulnerability/CVE-2025-64116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64116/
Summaries are generated and may contain mistakes; the official description above is the record.