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

> Authenticated attackers can inject persistent JavaScript into the QWKalkulation tool, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 13 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-8rrm-crhv-qpmv

## What is CVE-2024-45879?

CVE-2024-45879 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Nov 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

The file upload function in the "QWKalkulation" tool of baltic-it TOPqw Webportal v1.35.287.1 (fixed in version 1.35.291), in /Apps/TOPqw/QWKalkulation/QWKalkulation.aspx, is vulnerable to Cross-Site Scripting (XSS). To exploit the persistent XSS vulnerability, an attacker has to be authenticated to the application that uses the "TOPqw Webportal" as a software. When authenticated, the attacker can persistently place the malicious JavaScript code in the "QWKalkulation" menu.'

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

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


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

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

## Is CVE-2024-45879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45879 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45879 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-45879/ (Markdown: https://insights.sbomify.com/CVE-2024-45879/index.md)
```

## Sources

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

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