# CVE-2024-4028: Keycloak-core: stored xss in keycloak when creating a items in admin console

> A privileged attacker can inject malicious scripts via admin console items, leading to stored XSS and potential session hijacking.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 21 Nov 2025
- **Also known as:** ECHO-c42f-8476-7532, GHSA-q4xq-445g-g6ch

## What is CVE-2024-4028?

CVE-2024-4028 is a low-severity cross-site scripting vulnerability in Red Hat Build of Keycloak, published on 18 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in Keycloak. This issue may allow a privileged attacker to use a malicious payload as the permission while creating items (Resource and Permissions) from the admin console, leading to a stored cross-site scripting (XSS) attack.

Weakness: CWE-20 (Improper Input Validation)

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

2 open source packages ship an affected version, including org.keycloak:keycloak-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-core` | Maven | All versions to 26.1.2 | None |
| `org.keycloak:keycloak-core` | Maven | All versions to 26.1.2 | None |

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

Apply the vendor's patch.

## Is CVE-2024-4028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4028 is a low-severity cross-site scripting vulnerability in Red Hat Build of Keycloak, published on 18 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4028 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-core (Maven): affected all versions up to 26.1.2; no fix listed
- org.keycloak:keycloak-core (Maven): affected all versions up to 26.1.2; no fix listed

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-4028/ (Markdown: https://insights.sbomify.com/CVE-2024-4028/index.md)
```

## Sources

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

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