# CVE-2023-23628: Metabase subject to Exposure of Sensitive Information to an Unauthorized Actor

> Sandboxed users can view recipient lists for dashboard subscriptions, exposing sensitive user information to unauthorized actors.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A: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:** 28 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-492f-qxr3-9rrv

## What is CVE-2023-23628?

CVE-2023-23628 is a medium-severity vulnerability in metabase, published on 28 Jan 2023. 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. Affected versions are subject to Exposure of Sensitive Information to an Unauthorized Actor. Sandboxed users shouldn't be able to view data about other Metabase users anywhere in the Metabase application. However, when a sandbox user views the settings for a dashboard subscription, and another user has added users to that subscription, the sandboxed user is able to view the list of recipients for that subscription. This issue is patched in versions 0.43.7.1, 1.43.7.1, 0.44.6.1, 1.44.6.1, 0.45.2.1, and 1.45.2.1. There are no workarounds.

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

## Which versions are affected by CVE-2023-23628?

It affects 1 product.


Products: Metabase Metabase.

## How do I fix CVE-2023-23628?

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

## Is CVE-2023-23628 being exploited?

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

## Other vulnerabilities in 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-2023-23628 and fix it if it is affected.

What it is: CVE-2023-23628 is a medium-severity vulnerability in metabase, published on 28 Jan 2023. 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-2023-23628 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-2023-23628/ (Markdown: https://insights.sbomify.com/CVE-2023-23628/index.md)
```

## Sources

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

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