# CVE-2020-24550: Open redirect in n/a

> An attacker can redirect users to untrusted websites via a crafted URL parameter in Episerver Find, potentially facilitating phishing attacks.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** 31 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-384j-85hc-jfq2

## What is CVE-2020-24550?

CVE-2020-24550 is a medium-severity vulnerability in n/a, published on 31 Mar 2021. 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

An Open Redirect vulnerability in EpiServer Find before 13.2.7 allows an attacker to redirect users to untrusted websites via the _t_redirect parameter in a crafted URL, such as a /find_v2/_click URL.

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

## Which versions are affected by CVE-2020-24550?

It affects 1 product.


Products: Episerver Find.

## How do I fix CVE-2020-24550?

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

## Is CVE-2020-24550 being exploited?

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

Public exploit code:

- EpiServer Find <13.2.7 - Open Redirect (nuclei): http/cves/2020/CVE-2020-24550.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24550 and fix it if it is affected.

What it is: CVE-2020-24550 is a medium-severity vulnerability in n/a, published on 31 Mar 2021. 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-2020-24550 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-2020-24550/ (Markdown: https://insights.sbomify.com/CVE-2020-24550/index.md)
```

## Sources

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

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