CVE-2025-37732
BaseFortify
Publication date: 2025-12-15
Last updated on: 2025-12-18
Assigner: Elastic
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| elastic | kibana | From 7.0.0 (inc) to 7.17.29 (inc) |
| elastic | kibana | From 8.0.0 (inc) to 8.19.8 (exc) |
| elastic | kibana | From 9.0.0 (inc) to 9.1.8 (exc) |
| elastic | kibana | From 9.2.0 (inc) to 9.2.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-37732 is a Cross-site Scripting (XSS) vulnerability in Kibana that occurs due to improper neutralization of input during web page generation in the integration package upload functionality. This allows an authenticated user with Management permissions for Fleet and Integrations to inject and render malicious HTML content in another user's browser. It bypasses a previous fix related to HTML injection. [1]
How can this vulnerability impact me? :
This vulnerability can allow an authenticated user with certain permissions to inject malicious HTML content that will be rendered in other users' browsers. This can lead to unauthorized actions, data theft, or session hijacking within the affected Kibana environment. The impact includes limited confidentiality and integrity loss but no availability impact. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands or network/system detection methods provided for this vulnerability. Detection would generally involve verifying if your Kibana installation is within the affected versions and if unauthorized HTML injection attempts are observed, but no explicit commands are given.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade Kibana to a fixed version: 8.19.8, 9.1.8, or 9.2.2. No workarounds exist for users unable to upgrade, so applying the security update is essential to resolve the vulnerability. [1]