# CVE-2024-42915: Other in n/a

> Attackers can hijack user accounts by stealing password reset tokens via Host Header Injection in the Staff Appraisal System.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Aug 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-c9r7-wpw8-xc67

## What is CVE-2024-42915?

CVE-2024-42915 is a high-severity vulnerability in n/a, published on 23 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A host header injection vulnerability in Staff Appraisal System v1.0 allows attackers to obtain the password reset token via user interaction with a crafted password reset link. This will allow attackers to arbitrarily reset other users' passwords and compromise their accounts.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2024-42915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42915 is a high-severity vulnerability in n/a, published on 23 Aug 2024. Any signed-in user can exploit it over the network, 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-2024-42915 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-42915/ (Markdown: https://insights.sbomify.com/CVE-2024-42915/index.md)
```

## Sources

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

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