dbcve.org
KibanaApplication · Elastic

CVE-2025-25017

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 8.18.8 / 8.19.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation in Kibana can lead to Cross-Site Scripting (XSS)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a stored or reflected Cross-Site Scripting (XSS) vulnerability in Kibana where user-supplied input is not properly sanitized or encoded before being rendered in web pages. An attacker could inject malicious JavaScript that executes in the context of other users' sessions when they view the affected content.

MitigationApply the vendor patch for CVE-2025-25017 which implements proper input validation and output encoding in Kibana's web page generation routines. Until patched, restrict user access to untrusted content sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KibanaApplication
Affected:>= 7.0.0, < 8.18.8>= 8.19.0, < 8.19.4>= 9.0.0, < 9.0.7>= 9.1.0, < 9.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Kibana installation
    Check for Kibana binary in common paths: /usr/share/kibana/bin/kibana, /opt/kibana/bin/kibana, or run 'which kibana' on Linux. On Windows, check C:\Program Files\Kibana\bin\kibana.bat
    Affected if Kibana is not installed on the system
  2. Determine installed Kibana version
    Run 'kibana --version' from the Kibana bin directory, or check the version file at <kibana_install_path>/src/package.json, or check /usr/share/kibana/package.json
    Affected if Unable to retrieve version information
  3. Compare version against affected ranges
    Check if the installed version falls into any of these ranges: 7.0.0 to 8.18.7, 8.19.0 to 8.19.3, 9.0.0 to 9.0.6, or 9.1.0 to 9.1.3
    Affected if Version matches one of the affected ranges indicating potential vulnerability
  4. Verify Kibana web interface is accessible
    Confirm Kibana service is running and the web UI port (default 5601) is accessible: curl -I http://localhost:5601 or check if process is running: ps aux | grep kibana
    Affected if Kibana is running and accepting connections, making the XSS vulnerability exploitable

If Kibana is installed, running, and its version falls within 7.0.0-8.18.7, 8.19.0-8.19.3, 9.0.0-9.0.6, or 9.1.0-9.1.3, the environment is likely affected by this XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.18.8 / 8.19.4 / 9.0.7 or later
Fixed in 8.18.88.19.49.0.7
Interim mitigation

Apply the vendor patch for CVE-2025-25017 which implements proper input validation and output encoding in Kibana's web page generation routines. Until patched, restrict user access to untrusted content sources.

Recommended fix High confidence

Upgrade to the latest patch version in your respective branch: 8.18.8+ for 8.x, 8.19.4+ for 8.19.x, 9.0.7+ for 9.0.x, or 9.1.4+ for 9.1.x (or the latest 9.x release)

  1. 1. Identify the currently installed Kibana version using 'kibana --version' or the Kibana logs
  2. 2. Determine which version branch your installation belongs to (7.x, 8.19.x, 9.0.x, or 9.1.x)
  3. 3. For 7.x/8.x users: Upgrade to Kibana 8.18.8 or later
  4. 4. For 8.19.x users: Upgrade to Kibana 8.19.4 or later
  5. 5. For 9.0.x users: Upgrade to Kibana 9.0.7 or later
  6. 6. For 9.1.x users: Upgrade to Kibana 9.1.4 or later
  7. 7. After upgrade, verify Kibana starts successfully and test that the application functions normally
  8. 8. Validate the fix by checking the Kibana version (kibana --version) confirms the patched version is running
Caveat Upgrade within same major version should be low-risk; ensure Elasticsearch version compatibility before upgrading Kibana

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kibana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25017 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data