# CVE-2024-52283: Cross-site scripting in hackweek

> Attackers can inject malicious scripts via unsanitized inputs, leading to stored XSS attacks against users viewing specific projects.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/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:** 28 Nov 2024
- **Updated:** 28 Nov 2024
- **Also known as:** GHSA-q6p7-92g5-m4p4

## What is CVE-2024-52283?

CVE-2024-52283 is a medium-severity cross-site scripting vulnerability in SUSE hackweek, published on 28 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

Missing sanitation of inputs allowed arbitrary users to conduct a stored XSS attack that triggers for users that view a certain project

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

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


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

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

## Is CVE-2024-52283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52283 is a medium-severity cross-site scripting vulnerability in SUSE hackweek, published on 28 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-52283 in the wild and no public exploit code.

Affected product: SUSE hackweek. 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-52283/ (Markdown: https://insights.sbomify.com/CVE-2024-52283/index.md)
```

## Sources

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

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