LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37936: It was discovered that Kibana was not sanitizing document fields containing HTML snippets.

It was discovered that Kibana was not sanitizing document fields containing HTML snippets. Using this vulnerability, an attacker with the ability to write documents to an elasticsearch index could inject HTML. When the Discover app highlighted a search term containing the HTML, it would be rendered for the user.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-37936 is a stored cross-site scripting issue in Kibana. A user who can write documents into an Elasticsearch index could place HTML in fields. If another user searched in Kibana Discover and highlighting rendered that HTML, browser-side content could run or alter what the user sees.

Executive priority

Treat this as a moderate-priority remediation. It is not described as actively exploited, but unpatched Kibana environments with shared analytics access can expose staff to browser-side manipulation or data exposure.

Technical view

Kibana before 7.14.1 did not sanitize document fields containing HTML snippets during Discover search-term highlighting. The CVSS 3.1 score is 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact. CWE-79 applies.

Likely exposure

Exposure is likely limited to Kibana deployments before 7.14.1 where lower-privileged or untrusted users can write documents to Elasticsearch indexes that other users inspect in Discover.

Exploitation context

The source bundle does not show known active exploitation, and CISA KEV is false. Abuse requires index write access and a victim viewing highlighted search results in Discover, so business risk depends on who can write data and who reviews it.

Researcher notes

Focus on permission boundaries and data provenance. The key condition is attacker-controlled document content later rendered by Discover highlighting. Avoid assuming broader Elastic Stack compromise; the provided evidence supports Kibana-side XSS behavior only.

Mitigation direction

  • Upgrade Kibana to 7.14.1 or later per Elastic guidance.
  • Review Elastic security advisories for version-specific upgrade instructions.
  • Restrict Elasticsearch index write permissions to trusted users and services.
  • Limit Kibana Discover access to indexes containing untrusted submitted content.
  • Review role mappings for excessive index write privileges.

Validation and detection

  • Inventory all Kibana instances and confirm versions are 7.14.1 or later.
  • Identify indexes viewed in Discover that accept user-controlled or third-party data.
  • Review Elasticsearch roles for users with write access to those indexes.
  • Confirm Kibana users cannot access sensitive indexes unnecessarily.
  • Document compensating access controls if immediate upgrade is delayed.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37936 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2021-37936Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ElasticKibanaversions before 7.14.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.