# CVE-2024-55951: Metabase sandboxed users could see filter values from other sandboxed users

> Sandboxed users in Metabase can view filter values belonging to other sandboxed users, leading to unauthorized data disclosure.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Dec 2024
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-rhjf-q2qw-rvx3

## What is CVE-2024-55951?

CVE-2024-55951 is a medium-severity vulnerability in metabase, published on 16 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Metabase is an open-source data analytics platform. For new sandboxing configurations created in 1.52.0 till 1.52.2.4, sandboxed users are able to see field filter values from other sandboxed users. This is fixed in 1.52.2.5. Users on 1.52.0 or 1.52.1 or 1.5.2 should upgrade to 1.52.2.5. There are no workarounds for this issue aside from upgrading.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-55951?


## How do I fix CVE-2024-55951?

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

## Is CVE-2024-55951 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55951 and fix it if it is affected.

What it is: CVE-2024-55951 is a medium-severity vulnerability in metabase, published on 16 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-55951 in the wild and no public exploit code.

Affected product: 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-2024-55951/ (Markdown: https://insights.sbomify.com/CVE-2024-55951/index.md)
```

## Sources

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

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