Categories
CVE-2025-25018 high CVSS 8.7

Cross-Site Scripting (XSS) in Elastic Kibana (CVE-2025-25018)

Summary

Cross-site scripting in Elastic Kibana (CVE-2025-25018). Confidential information can be exposed externally.

Original description

The description as published by the source.

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

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-25018 has been found in Elastic Kibana.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Elastic Kibana CVE-2025-25018" on the vendor's site.

CVE-2025-25018 (Elastic Kibana) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in Elastic Kibana.

📍 Affected scope

Check the vendor advisory for the affected versions of Elastic Kibana.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kibana' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'Kibana' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kibana を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami kibana
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.18.8"},{"introduced":"8.19.0"},{"fixed":"8.19.5"},{"introduced":"9.0.0"},{"fixed":"9.0.8"},{"introduced":"9.1.0"},{"fixed":"9.1.5"}]}]
Bitnami elk
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.18.8"},{"introduced":"8.19.0"},{"fixed":"8.19.5"},{"introduced":"9.0.0"},{"fixed":"9.0.8"},{"introduced":"9.1.0"},{"fixed":"9.1.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details