Cyber Resilience

CVE-2025-37732

XSS in Elastic Kibana 7.0.0 – 7.17.29

Published
15 December 2025
Modified
18 December 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-37732 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Elastic Kibana. Its CVSS base score is 5.4 (Medium).

Operationally, ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper neutralization of input during web page generation ('Cross-site Scripting') (CWE-79) allows an authenticated user to render HTML tags within a user’s browser via the integration package upload functionality. This issue is related to ESA-2025-17 (CVE-2025-25018) bypassing that fix to…

more

achieve HTML injection.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-22972Shared CWE-79
CVE-2023-4482Shared CWE-79
CVE-2023-48472Shared CWE-79
CVE-2023-4175Shared CWE-79
CVE-2023-50833Shared CWE-79
CVE-2023-30097Shared CWE-79
CVE-2023-36656Shared CWE-79
CVE-2023-2477Shared CWE-79
CVE-2023-46783Shared CWE-79
CVE-2023-3476Shared CWE-79

Affected Assets

elastic
kibana
7.0.0 — 7.17.29 · 8.0.0 — 8.19.8 · 9.0.0 — 9.1.8

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-15 Information Output Filtering
  • SI-7 Software, Firmware, and Information Integrity
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation and sanitization of all input (including uploaded integration packages) to prevent improper neutralization that leads to HTML/XSS injection.

prevent

Requires filtering or encoding of information output during web page generation, blocking the rendering of attacker-supplied HTML tags in user browsers.

preventdetect

Mandates integrity verification of software/information (e.g., uploaded packages) before processing, reducing the chance that malicious or malformed content bypasses prior fixes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

none

Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.

References