Kibana version 5.4.0 was affected by a Cross Site Scripting (XSS) bug in the Time Series Visual Builder.

published 2017-06-05 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17390

cvss: 6.1; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 0; none known

Kibana version 5.4.0 was affected by a Cross Site Scripting (XSS) bug in the Time Series Visual Builder. This bug could allow an attacker to obtain sensitive information from Kibana users.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-8439 updated 2026-05-13 cvss 6.1

kibana: XSS in Time Series Visual Builder could allow an attacket to obtain sensitive user information

Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) Operational Tools kibana Red Hat OpenShift Enterprise 3 kibana Red Hat OpenStack Platform 8 (Liberty) Operational Tools kibana Red Hat OpenStack Platform 9 (Mitaka) Operational Tools kibana Red Hat OpenStack Platform 10 (Newton) Operational Tools kibana
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.1	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

Elastic Kibana

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

elastic.co /blog/kibana-5-4-1-and-5-3-3-released
release-notes, vendor-advisory
discuss.elastic.co /t/elastic-stack-5-4-1-and-5-3-3-security-updates/87952
mitigation, vendor-advisory
elastic.co /community/security
vendor-advisory

Sources

CVE List CVE-2017-8439
NVD CVE-2017-8439

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary