dbcve.org
KibanaApplication · Elastic

CVE-2025-25018

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 8.18.8 / 8.19.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 stored 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

Kibana contains a stored Cross-Site Scripting (XSS) vulnerability caused by improper neutralization of user input during web page generation. An attacker with low-privilege access could inject malicious scripts that execute in the browsers of other users viewing the affected content.

MitigationApply the vendor patch for CVE-2025-25018 which implements proper input sanitization and output encoding in Kibana's web page generation components.

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.5>= 9.0.0, < 9.0.8>= 9.1.0, < 9.1.5

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Kibana version
    Run 'bin/kibana --version' from the Kibana installation directory, or check the version field in the Kibana status API at /api/status
    Affected if The installed version falls within any of these ranges: >= 7.0.0 and < 8.18.8; >= 8.19.0 and < 8.19.5; >= 9.0.0 and < 9.0.8; >= 9.1.0 and < 9.1.5
  2. Confirm web interface is enabled
    Verify the Kibana server is running and the UI is accessible by accessing the Kibana URL in a browser or checking that the HTTP service is listening on the configured port
    Affected if The Kibana web interface is exposed and users can access it to view content where injected scripts could execute
  3. Identify low-privilege user access
    Check if there are users with low-privilege roles (such as viewer, reader, or basic read-only access) who can create or edit content that gets stored and rendered in the Kibana interface
    Affected if Low-privilege users exist who can input content that is stored and displayed to other users, enabling the stored XSS attack vector

You are affected if your Kibana version is within the affected ranges AND the web interface is accessible to users who could inject malicious scripts that execute in other users' browsers.

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.5 / 9.0.8 or later
Fixed in 8.18.88.19.59.0.8
Interim mitigation

Apply the vendor patch for CVE-2025-25018 which implements proper input sanitization and output encoding in Kibana's web page generation components.

Recommended fix High confidence

Upgrade to Kibana 8.18.8, 8.19.5, 9.0.8, or 9.1.5 (depending on current major version branch)

  1. 1. Identify the current Kibana version by running: kibana --version or checking the kibana package.json
  2. 2. Determine which upgrade path applies based on current version: if >= 7.0.0 and < 8.18.8 upgrade to 8.18.8; if >= 8.19.0 and < 8.19.5 upgrade to 8.19.5; if >= 9.0.0 and < 9.0.8 upgrade to 9.0.8; if >= 9.1.0 and < 9.1.5 upgrade to 9.1.5
  3. 3. Back up Kibana configuration files (kibana.yml) and any custom dashboards, visualizations, or saved objects
  4. 4. Stop the Kibana service: systemctl stop kibana or sudo service kibana stop
  5. 5. For package manager installations (apt/yum): sudo apt-get update && sudo apt-get install kibana=8.18.8 or sudo yum install kibana-8.18.8
  6. 6. For tar.gz installations: download the new version from https://www.elastic.co/downloads/kibana, extract, and replace the installation directory
  7. 7. Review kibana.yml for any version-specific configuration changes in the Kibana upgrade guide
  8. 8. Start the Kibana service: systemctl start kibana or sudo service kibana start
Caveat Review Elastic Stack compatibility matrix - ensure Elasticsearch version is compatible with the target Kibana version; some plugin APIs may have changed

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

Fix this in Kibana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25018 — 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-25018 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