Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-72899 – Unauthenticated SQL Injection – Metabase v58.0–58.23, v59.0–59.20, v60.0–60.16, v61

Be the first to know when new zero-days emerge:

Summary

CVE-2026-72899 is an unauthenticated SQL injection vulnerability (CWE-89) in Metabase. An attacker can inject arbitrary SQL through a publicly shared card or dashboard that exposes a field-filter (dimension) parameter, gaining access to the Metabase application database. It carries a CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: Improper neutralization of input supplied to field-filter (dimension) parameters on publicly shared cards and dashboards, allowing attacker-controlled SQL to reach the application database.
  • Trigger conditions: A card or dashboard is published via public sharing and exposes a field-filter parameter; the attacker submits a crafted value to that parameter. No authentication is required.
  • Attack vector: Network — the malicious request is sent to the publicly accessible shared link.
  • Impact: Injection of arbitrary SQL into the Metabase application database, enabling attackers to alter configuration, steal stored credentials for connected databases, read data accessible through those connections, and export data.

Affected software

  • Metabase v58.0 through v58.23
  • Metabase v59.0 through v59.20
  • Metabase v60.0 through v60.16
  • Metabase v61.0 through v61.10
  • Metabase v62.0 through v62.8
  • Metabase v63.0 through v63.4

Severity

  • CVSS v3.1 base score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to a patched release — v58.24, v59.21, v60.17, v61.11, v62.9, or v63.5.
  • If no patch can be applied yet: Temporarily disable public sharing or unpublish any public cards and dashboards that expose field-filter parameters.
  • Post-upgrade hardening: Revoke active user sessions, review and rotate API keys, audit administrator accounts for unauthorized changes, rotate credentials for connected databases, and review access and query logs for signs of exploitation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: window.MetabaseBootstrap =, MetabaseBootstrap, "tag": "v

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge