Kibana ReportingApplication · Elastic
CVE-2016-1000218
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 · uneditedKibana Reporting plugin version 2.4.0 is vulnerable to a CSRF vulnerability that could allow an attacker to generate superfluous reports whenever an authenticated Kibana user navigates to a specially-crafted page.
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 confidenceKibana Reporting plugin version 2.4.0 contains a CSRF vulnerability that allows remote attackers to trigger unauthorized report generation on behalf of authenticated users. By tricking a logged-in Kibana user into visiting a malicious webpage, attackers can make the user's browser send requests to the Reporting plugin endpoint, causing the server to generate reports without the user's consent.
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
Kibana ReportingApplication
= 2.4.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Kibana installation and versionCheck the installed Kibana version by examining Kibana package metadata, configuration files, or the running service. Common methods include checking the Kibana banner on startup, querying the /api/status endpoint, or examining the kibana package.json file.Affected if The installed Kibana version is exactly 2.4.0
-
Confirm Reporting plugin is enabledVerify that the Kibana Reporting plugin is installed and active. This can be done by checking the Kibana plugins directory, examining the kibana.yml configuration for reporting settings, or querying the /api/reporting endpoints.Affected if The Reporting plugin is present and enabled in the Kibana installation
-
Check Reporting endpoint accessibilityIdentify if the Reporting plugin endpoints are accessible without CSRF protection. Attempt to access the report generation endpoint or examine the server configuration for the reporting routes.Affected if The Reporting plugin endpoints are accessible and accept requests without anti-CSRF token validation
-
Verify session cookie configurationInspect the Kibana configuration (kibana.yml) and the session cookies used by Kibana to determine if SameSite attributes are configured.Affected if Session cookies do not have SameSite attributes configured or set to 'None'
A user is affected if they are running Kibana version 2.4.0 with the Reporting plugin enabled, as this specific version contains the CSRF vulnerability in the reporting endpoint.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the Kibana Reporting plugin to a version that includes CSRF protection (anti-CSRF tokens) and implement SameSite cookie attributes for session cookies. If upgrade is not immediately feasible, consider disabling the reporting feature or implementing temporary network-level controls to restrict reporting endpoint access.
Fix this in Kibana Reporting
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1000218 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1000218 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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