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

> An attacker can execute arbitrary scripts in the victim's browser via the login page of WebLaudos, potentially leading to session hijacking or data theft.

- **Severity:** Medium 5.4 (`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:** 5 Nov 2024
- **Updated:** 5 Nov 2024
- **Also known as:** GHSA-2hfc-prjx-wjcx

## What is CVE-2024-48312?

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

WebLaudos v20.8 (118) was discovered to contain a cross-site scripting (XSS) vulnerability via the login page.

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

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


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

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

## Is CVE-2024-48312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48312 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48312 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-48312/ (Markdown: https://insights.sbomify.com/CVE-2024-48312/index.md)
```

## Sources

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

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