How severe is CVE-2014-3656?

CVE-2014-3656 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-3656?

CVE-2014-3656 affects the following packages: org.keycloak:keycloak-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3656?

Update org.keycloak:keycloak-core to 1.1.0.Beta1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3656 is resolved across your whole dependency graph.

How do I detect CVE-2014-3656 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-3656 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2014-3656 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3656 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-3656?

CVE-2014-3656 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-3656?

CVE-2014-3656 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-3656 published, and has it been updated?

CVE-2014-3656 was published on May 17, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2014-3656 — keycloak-core

MEDIUMFix: keycloak/keycloak@63b41e2

CVE-2014-3656 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.

JBoss KeyCloak Cross-site Scripting Vulnerability

Published

May 17, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.keycloak:keycloak-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.keycloak:keycloak-core`	all versions	1.1.0.Beta1`org.keycloak:keycloak-core:1.1.0.Beta1`

Affected Products

1 product · 1 configurations

Application

jboss keycloakredhat

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-core to 1.1.0.Beta1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3656 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2014-3656 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

keycloak

9.3/10

Maintained10/10

Code-Review10/10

Branch-Protection8/10

Assessed Oct 26, 2026

Timeline

Disclosed

May 17, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2014-3656

References

Advisorynvd.nist.gov · CVE 2014 3656 Webgithub.com · 63b41e2548cbc20bd3758e34a82d880e177bf24c Webaccess.redhat.com · cve 2014 3656 Webbugzilla.redhat.com · show bug.cgi Webissues.jboss.org · KEYCLOAK 703 Websecurity.snyk.io · SNYK JAVA ORGKEYCLOAK 31231

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting keycloak-core are rated as high or higher (top: high).

CVE-2024-4028CVE-2024-10039CVE-2024-7318CVE-2023-6841CVE-2024-7260CVE-2023-6927CVE-2023-4918CVE-2023-0105

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024