# CVE-2024-25715: Open redirect in n/a

> Attackers can redirect users to malicious sites via the redirect_uri parameter in Glewlwyd SSO server, 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:** Yes
- **Published:** 11 Feb 2024
- **Updated:** 16 Jun 2025
- **Also known as:** DEBIAN-CVE-2024-25715, GHSA-vxrh-jfch-hqcf, UBUNTU-CVE-2024-25715

## What is CVE-2024-25715?

CVE-2024-25715 is a medium-severity vulnerability in n/a, published on 11 Feb 2024. 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

Glewlwyd SSO server 2.x through 2.7.6 allows open redirection via redirect_uri.

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

## Which versions are affected by CVE-2024-25715?

It affects 1 product.


Products: Glewlwyd Sso Server Project Glewlwyd Sso Server.

## How do I fix CVE-2024-25715?

Upgrade to a fixed version.

## Is CVE-2024-25715 being exploited?

There is no known exploitation of CVE-2024-25715 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-49208](https://insights.sbomify.com/CVE-2023-49208/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-27240](https://insights.sbomify.com/CVE-2022-27240/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-40818](https://insights.sbomify.com/CVE-2021-40818/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25715 and fix it if it is affected.

What it is: CVE-2024-25715 is a medium-severity vulnerability in n/a, published on 11 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-25715 in the wild and no public exploit code.

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-2024-25715/ (Markdown: https://insights.sbomify.com/CVE-2024-25715/index.md)
```

## Sources

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

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