Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Metabase-Setup-Endpoint-SQLi-Fix — Fixes unauthenticated SQL injection in a setup endpoint by replacing raw JDBC queries with ORM parameterization and constant-time token validation. | Kitploit
Tools/GitHubGitHub/ubitquity/metabase-setup-endpoint-sqli-fix
Defensive ToolsVulnerability AnalysisWeb SecurityAuthenticationAPI SecurityDatabase Security
GitHububitquity/metabase-setup-endpoint-sqli-fix

Metabase-Setup-Endpoint-SQLi-Fix

Fixes unauthenticated SQL injection in a setup endpoint by replacing raw JDBC queries with ORM parameterization and constant-time token validation.

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
View Repository
1525 days agoNot yet reviewed
Share

CVE-2026-72898: Metabase Setup Endpoint SQLi Patch

This repository contains the hotfix for CVE-2026-72898, an unauthenticated SQL Injection vulnerability in the setup endpoint of self-hosted Metabase instances.

Left unpatched, attackers can bypass the setup token validation, execute arbitrary database commands, and extract data warehouse credentials.

The Root Cause

The validate-setup-token function previously accepted unvalidated user input and concatenated it directly into a raw JDBC string. This allowed an attacker to break out of the SQL string and append malicious commands.

Patch Architecture

This patch fundamentally shifts the validation mechanism to neutralize SQL injection vectors:

  1. ORM Integration: Migrates database queries from raw strings to Toucan 2 (t2), Metabase's native Object-Relational Mapper.
  2. Input Isolation: The system no longer passes user input into the database to verify the token. Instead, it queries the database for the expected token using strict parameterization.
  3. In-Memory Validation: Uses crypto.equality/eq? to compare the tokens in application memory (Clojure) rather than in the database.
  4. Timing Attack Resistance: The crypto.equality/eq? function executes in constant time, preventing attackers from brute-forcing the token via timing discrepancies.

Implementation Details

Replaces the vulnerable raw jdbc/query logic in metabase.api.setup.

License

Metabase is licensed under the AGPL. This patch is provided under the same terms.

Download Tool