Skip to main content
VulnerabilityPublished

CVE-2025-25009: Elastic Kibana · XSS or 'Cross-site Scripting'

Affects Elastic KibanaSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Elastic KibanaAffected
  • 7.0.0 – 9.1.0
5 affected builds
Fixed in–

AI-suggested

  1. Monitor Elastic's official channels for patches and apply them immediately upon release to affected Kibana versions.
  2. Until patches are available, restrict file upload permissions to trusted users only and limit the types of files accepted to reduce attack surface.
  3. Implement strict input validation and sanitization on all user inputs, especially file metadata and case file contents.
  4. Deploy Content Security Policies (CSP) to restrict execution of unauthorized scripts within Kibana interfaces.
  5. Conduct regular security audits and penetration testing focusing on web application vulnerabilities in Kibana deployments.
  6. Enable multi-factor authentication (MFA) to reduce risk from compromised credentials.
  7. Monitor logs and user activity for unusual behavior indicative of exploitation attempts.
  8. Educate users about the risks of interacting with untrusted content within Kibana dashboards.
  9. Consider network segmentation to isolate Kibana instances and limit lateral movement in case of compromise.
  10. Review and harden Kibana configuration settings to minimize exposure of sensitive data and administrative functions.

Description

Improper Neutralization of Input During Web Page Generation in Kibana can lead to Stored XSS via case file upload.

References

Community reviews

Loading reviews…