# CVE-2024-4812: Katello: potential cross-site scripting exploit in ui

> Attackers can inject malicious JavaScript into user descriptions, leading to script execution when viewing specific pages in Red Hat Satellite.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jun 2024
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-jjqv-cfcp-2xj7

## What is CVE-2024-4812?

CVE-2024-4812 is a medium-severity cross-site scripting vulnerability in Redhat Satellite, published on 5 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the Katello plugin for Foreman, where it is possible to store malicious JavaScript code in the "Description" field of a user. This code can be executed when opening certain pages, for example, Host Collections.

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

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

It affects 2 products.


Products: Katello Project Katello, Redhat Satellite.

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

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

## Is CVE-2024-4812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4812 is a medium-severity cross-site scripting vulnerability in Redhat Satellite, published on 5 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-4812 in the wild and no public exploit code.

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

## Sources

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

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