JBoss KeyCloak Cross-site Scripting Vulnerability
If a JBoss Keycloak application was configured to use * as a permitted web origin in the Keycloak administrative console, crafted requests to the login-status-iframe.html endpoint could inject arbitrary Javascript into the generated HTML code via the "origin" query parameter, leading to a cross-site scripting (XSS) vulnerability.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.keycloak:keycloak-core | < 1.1.0.Beta1 | 1.1.0.Beta1 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2014-3656
- https://github.com/keycloak/keycloak/commit/63b41e2548cbc20bd3758e34a82d880e177bf24c
- https://access.redhat.com/security/cve/cve-2014-3656
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-3656
- https://issues.jboss.org/browse/KEYCLOAK-703
- https://security.snyk.io/vuln/SNYK-JAVA-ORGKEYCLOAK-31231
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Weakness (CWE)
CWE-79- Platform
- Java / Kotlin (Maven)
- Package
org.keycloak:keycloak-core- Disclosed
- 17.05.2022
- Updated
- 11.10.2026 11:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-px42-mr8m-cpgh - CC BY 4.0
Vulnerability history: org.keycloak:keycloak-core
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 49
- First → latest
- 10.2018 02.2025
- Without a fix
- 5
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- High 14
- Medium 31
- Low 1
Disclosures per year
- 2018: 9
- 2019: 4
- 2020: 4
- 2021: 5
- 2022: 17
- 2023: 4
- 2024: 5
- 2025: 1
- 2026: 0
-
JBoss KeyCloak Cross-site Scripting Vulnerability this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.