# CVE-2018-0697: Cross-site scripting in Metabase

> Remote attackers can inject arbitrary web script or HTML into Metabase, potentially leading to code execution or data theft.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2446-mrf6-p2h8

## What is CVE-2018-0697?

CVE-2018-0697 is a medium-severity cross-site scripting vulnerability in Metabase, Inc. Metabase, published on 15 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerability in Metabase version 0.29.3 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-0697?

It affects 1 product.


Products: Metabase Metabase.

## How do I fix CVE-2018-0697?

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

## Is CVE-2018-0697 being exploited?

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

## Other vulnerabilities in Metabase, Inc. Metabase

- [CVE-2026-72898](https://insights.sbomify.com/CVE-2026-72898/): Metabase SQL Injection (critical 10.0, exploited in the wild)
- [CVE-2021-41277](https://insights.sbomify.com/CVE-2021-41277/): Metabase GeoJSON API Local File Inclusion (critical 10.0, exploited in the wild)
- [CVE-2026-50148](https://insights.sbomify.com/CVE-2026-50148/): Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write (critical 10.0)
- [CVE-2023-37470](https://insights.sbomify.com/CVE-2023-37470/): Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint (critical 10.0)
- [CVE-2026-59827](https://insights.sbomify.com/CVE-2026-59827/): Metabase: Unsafe Deserialization of H2 Query Results (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0697 and fix it if it is affected.

What it is: CVE-2018-0697 is a medium-severity cross-site scripting vulnerability in Metabase, Inc. Metabase, published on 15 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0697 in the wild and no public exploit code.

Affected product: Metabase, Inc. Metabase. 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-2018-0697/ (Markdown: https://insights.sbomify.com/CVE-2018-0697/index.md)
```

## Sources

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

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