# CVE-2024-46073: Cross-site scripting in n/a

> Reflected XSS in IceHRM login page allows attackers to execute arbitrary JavaScript via the next parameter.

- **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:** 6 Jan 2025
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-x492-3p6g-fmvm

## What is CVE-2024-46073?

CVE-2024-46073 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Jan 2025. 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

A reflected Cross-Site Scripting (XSS) vulnerability exists in the login page of IceHRM v32.4.0.OS. The vulnerability is due to improper sanitization of the "next" parameter, which is included in the application's response without adequate escaping. An attacker can exploit this flaw by tricking a user into visiting a specially crafted URL, causing the execution of arbitrary JavaScript code in the context of the victim's browser. The issue occurs even though the application has sanitization mechanisms in place.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-46073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-46073 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Jan 2025. 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-2024-46073 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-46073/ (Markdown: https://insights.sbomify.com/CVE-2024-46073/index.md)
```

## Sources

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

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