dbcve.org
KibanaApplication · Elastic

CVE-2025-25009

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-07
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 XSS via case file upload.

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 · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Kibana's case file upload functionality. The application fails to properly neutralize input during web page generation, allowing attackers to embed malicious scripts in uploaded files that execute when other users view the case content.

MitigationApply the vendor patch/update for Kibana to remediate the input validation flaw. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure to mitigate XSS risks.

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 installed Kibana version
    Check the Kibana version by querying the Kibana status API endpoint (for example, GET /api/status) or by reviewing the Kibana package.json file in the installation directory.
    Affected if The installed version falls within any of the affected ranges: >=7.0.0 and <8.18.8, >=8.19.0 and <8.19.5, >=9.0.0 and <9.0.8, or >=9.1.0 and <9.1.5.
  2. Confirm Cases feature is enabled
    Review the Kibana configuration file (kibana.yml) for the cases configuration, or query the Kibana features API to check if the cases feature is active in the environment.
    Affected if The Cases feature is enabled and accessible to users in the Kibana environment.
  3. Verify file attachments are permitted on cases
    Check the Kibana cases settings via the UI under Stack Management > Kibana > Cases, or review the kibana.yml configuration for case attachment settings.
    Affected if File upload or attachment functionality is enabled for cases, allowing users to attach files to case entries.
  4. Inspect existing case attachments for suspicious content
    Query the Elasticsearch index backing Kibana cases (typically .kibana-event-log-* or cases indices) to list attachments stored on existing cases, or use the Kibana Cases UI to review any files already uploaded to cases.
    Affected if Any files have been uploaded to cases in the environment, particularly files with filenames or content that may contain HTML, JavaScript, or other executable script patterns.

You are affected if your Kibana version is within the affected version ranges AND the Cases feature with file upload is enabled and any case contains uploaded attachments that could contain malicious scripts.

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/update for Kibana to remediate the input validation flaw. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure to mitigate XSS risks.

Recommended fix High confidence

Upgrade to 8.18.8 (for 7.x/8.x users), 8.19.5 (for 8.19.x users), 9.0.8 (for 9.0.x users), or 9.1.5 (for 9.1.x users)

  1. 1. Back up your Kibana configuration and any custom dashboards/visualizations
  2. 2. Ensure your Elasticsearch cluster is running a compatible version before upgrading Kibana
  3. 3. Stop the Kibana service
  4. 4. Upgrade Kibana to the appropriate fixed version based on your current major version
  5. 5. Verify the Kibana service starts successfully
  6. 6. Test that case file upload functionality works correctly and that XSS payloads are properly neutralized
Caveat Review Elastic Stack compatibility matrix before upgrading; major version upgrades may require migration steps for saved objects and plugins

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
  • Testing8.0 h
  • Review / QA8.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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