# CVE-2025-63784: Open redirect in n/a

> Attackers can redirect authenticated users to malicious sites via manipulated headers, enabling phishing attacks in the Onlook web application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-r4cg-5xmx-26h7

## What is CVE-2025-63784?

CVE-2025-63784 is a medium-severity vulnerability in n/a, published on 7 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Open Redirect vulnerability exists in the OAuth callback handler in file onlook/apps/web/client/src/app/auth/callback/route.ts in Onlook web application 0.2.32. The vulnerability occurs because the application trusts the X-Forwarded-Host header value without proper validation when constructing a redirect URL. A remote attacker can send a manipulated X-Forwarded-Host header to redirect an authenticated user to an arbitrary external website under their control, which can be exploited for phishing attacks.

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

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

It affects 1 product.


Products: Onlook Onlook.

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

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

## Is CVE-2025-63784 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63783](https://insights.sbomify.com/CVE-2025-63783/): Missing authorization in n/a (high 7.6)
- [CVE-2025-63785](https://insights.sbomify.com/CVE-2025-63785/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63784 is a medium-severity vulnerability in n/a, published on 7 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63784 exists.

Affected product: n/a. 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-63784/ (Markdown: https://insights.sbomify.com/CVE-2025-63784/index.md)
```

## Sources

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

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