Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
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.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-72898-metabase — Python checker and active PoC for CVE-2026-72898 in Metabase: detects version and SQL error indicators, then tests SQLi against the password reset endpoint. | Kitploit
Tools/GitHubGitHub/gagaltotal/cve-2026-72898-metabase
Vulnerability ScannersWeb Vulnerability ScannersExploitationWeb Application ExploitationPenetration Testing
GitHubgagaltotal/cve-2026-72898-metabase

CVE-2026-72898-metabase

Python checker and active PoC for CVE-2026-72898 in Metabase: detects version and SQL error indicators, then tests SQLi against the password reset endpoint.

View RepositoryWebsite
1 month agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    911
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    707
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    431
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    405
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    352
  • 6

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    342

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-72898 Metabase Security Tools

A collection of two Python scripts to help check the suspected impact of CVE-2026-72898 on Metabase instances. The vulnerable version information used by the checker is embedded in the script and is not a substitute for official advisories or manual testing.

Usage warning

Use only on systems you own, lab environments, or systems that explicitly permit this testing. You are responsible for ensuring permission, scope, and testing rules before running either script.

The checker sends HTTP requests and probes in the form of SQLi input. Although it is not designed to create an administrator session, these requests may still be recorded in logs or trigger application behavior. The PoC is an active test: the script sends SQLi payloads and attempts to verify an administrator session. PoC testing may alter data or session state on the target. Do not run the PoC on production systems or third-party targets without written consent and a recovery plan.

Project contents

FilePurpose
CVE-2026-72898-checker.pyAccessibility-based check, Metabase identification, detected version, and SQL error indicators. Results can be saved as JSON.
CVE-2026-72898-poc.pyActive three-step test: checks the service, sends a payload to the password reset endpoint, then checks whether an administrator session is accepted. Results can be saved as TSV.

Both scripts have different options and result formats. Run --help to see the options available directly from the script version in this workspace.

Requirements

  • Python 3
  • The Python package requests (this package also installs the urllib3 dependency used by the PoC)
  • Network connectivity to the authorized target

Installation

Using a virtual environment is recommended:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install requests

In Windows PowerShell, activate the environment with:

.venv\Scripts\Activate.ps1

Using the checker

Check a single URL:

python CVE-2026-72898-checker.py --url https://metabase.example.test

Check several URLs from the file, one URL per line. Empty lines and lines starting with # are skipped:

https://metabase-lab-1.example.test
# instance lab kedua
http://192.0.2.20:3000
python CVE-2026-72898-checker.py --file targets.txt --output hasil_scan.json

Opsi tambahan:

python CVE-2026-72898-checker.py --url https://metabase.example.test --timeout 20 --delay 2 --verbose
  • --timeout: batas waktu request dalam detik; default 15.
  • --delay: jeda antar target dalam detik; default 1.0.
  • --verbose: tampilkan detail diagnostik.
  • --no-verify-ssl: nonaktifkan validasi sertifikat TLS. Gunakan hanya di lab ketika memang diperlukan.
  • --output: simpan laporan JSON.

Checker menolak penggunaan --url dan --file secara bersamaan. Kode keluar yang diterapkan: 0 jika tidak ada status VULNERABLE atau ERROR, 1 jika ada error, dan 2 jika ada temuan VULNERABLE.

Penggunaan PoC

PoC melakukan pengujian aktif. Jalankan hanya pada target yang secara eksplisit diizinkan:

python CVE-2026-72898-poc.py --target http://metabase-lab.example.test:3000

For the list of targets:

http://metabase-lab-1.example.test:3000
# target lab lain
http://192.0.2.30:3000
python CVE-2026-72898-poc.py --targets targets.txt --output hasil_poc.tsv --timeout 20
  • --target / -t: a single target URL.
  • --targets / -T: target file, one URL per line; if both are provided, the file is used.
  • --output / -o: save results as tab-separated (TSV).
  • --timeout: request timeout in seconds; default 15.
  • --verbose / -v: show additional diagnostics, including request and payload details.

The PoC disables TLS certificate validation for all requests. Do not assume that the HTTPS connections used by the PoC have verified the server's identity. Verbose mode can display highly sensitive data; avoid enabling it unless needed and do not share raw output.

Reading results

The checker returns statuses such as VULNERABLE, PATCHED, NOT_AFFECTED, LIKELY_SAFE, NOT_METABASE, ENDPOINT_NOT_FOUND, or ERROR. The LIKELY_SAFE status is not proof that the target is safe. The VULNERABLE status may be based on the version embedded in the checker or SQL error indicators; results need to be confirmed against the official advisory and the target's actual configuration.

The PoC reports vulnerable or statuses such as patched, not_vulnerable, unknown, timeout, and error. A not_vulnerable result does not prove that all vulnerability conditions have been eliminated.

PoC result files may contain session IDs and administrator email addresses. Treat JSON/TSV reports, target files, and verbose logs as sensitive data: restrict access, store them securely, and delete them according to organizational policy once the audit need is complete.

Limitations

  • Results depend on network responses, proxies, Metabase configuration, and the detectable version.
  • The version ranges in the checker are static data within the script and may become outdated or may not cover all editions/builds.
  • Automated checks do not replace vendor advisories, manual verification, or configuration audits.
  • There is no guarantee that active testing is free of side effects. Use an isolated environment and appropriate recovery procedures.

Response if there are indications of a vulnerability

Stop active testing, securely preserve the minimum necessary evidence, and inform the system owner through approved channels. Validate the version against the official Metabase advisory, then prioritize updating to a fixed release according to vendor guidance. If an administrator session may have been established, the system owner should revoke related sessions, review logs and account activity, and follow internal incident response procedures.

Download Tool