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

> Attackers can inject host headers to redirect password reset links, leaking tokens and potentially taking over user accounts.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2024
- **Updated:** 26 Aug 2024
- **Also known as:** GHSA-pr2m-hg7m-28mp

## What is CVE-2024-42914?

CVE-2024-42914 is a critical vulnerability in n/a, published on 23 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A host header injection vulnerability exists in the forgot password functionality of ArrowCMS version 1.0.0. By sending a specially crafted host header in the forgot password request, it is possible to send password reset links to users which, once clicked, lead to an attacker-controlled server and thus leak the password reset token. This may allow an attacker to reset other users' passwords.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Arrowjs Arrowcms.

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

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

## Is CVE-2024-42914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42914 is a critical vulnerability in n/a, published on 23 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42914 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-2024-42914/ (Markdown: https://insights.sbomify.com/CVE-2024-42914/index.md)
```

## Sources

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

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