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

> Attackers can redirect users to arbitrary websites via crafted links on the login page, potentially facilitating phishing attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 11 Apr 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-w9jr-g766-pf8c

## What is CVE-2024-27592?

CVE-2024-27592 is a medium-severity vulnerability in n/a, published on 11 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open Redirect vulnerability in Corezoid Process Engine v6.5.0 allows attackers to redirect to arbitrary websites via appending a crafted link to /login/ in the login page URL.

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

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

It affects 1 product.


Products: Corezoid Corezoid.

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

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

## Is CVE-2024-27592 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27592 is a medium-severity vulnerability in n/a, published on 11 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27592 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-27592/ (Markdown: https://insights.sbomify.com/CVE-2024-27592/index.md)
```

## Sources

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

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