# CVE-2019-7616: Server-side request forgery in Kibana

> Administrative users can exploit a Timelion configuration flaw to perform server-side request forgery, accessing external resources via the Kibana host.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cjvv-mvp7-x62q

## What is CVE-2019-7616?

CVE-2019-7616 is a medium-severity server-side request forgery vulnerability in Elastic Kibana, published on 30 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Kibana versions before 6.8.2 and 7.2.1 contain a server side request forgery (SSRF) flaw in the graphite integration for Timelion visualizer. An attacker with administrative Kibana access could set the timelion:graphite.url configuration option to an arbitrary URL. This could possibly lead to an attacker accessing external URL resources as the Kibana process on the host system.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-7616?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2019-7616?

No fix has been published for CVE-2019-7616 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-7616 being exploited?

There is no known exploitation of CVE-2019-7616 in the wild and no public exploit code.

Public exploit code:

- POC for CVE-2019-7616 / ESA-2019-09 (github_poc): https://github.com/random-robbie/CVE-2019-7616

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7616 and fix it if it is affected.

What it is: CVE-2019-7616 is a medium-severity server-side request forgery vulnerability in Elastic Kibana, published on 30 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7616 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-7616/ (Markdown: https://insights.sbomify.com/CVE-2019-7616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-7616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-7616
- OSV: https://osv.dev/vulnerability/CVE-2019-7616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-7616/
Summaries are generated and may contain mistakes; the official description above is the record.