Incident Score: Analysis & Impact (MET1786299845)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Metabase's Vulnerability and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Metabase Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Metabase breach identified under incident ID MET1786299845.
The analysis begins with a detailed overview of Metabase's information like the linkedin page: https://www.linkedin.com/company/metabase, the number of followers: 27525, the industry type: Data Infrastructure and Analytics and the number of employees: 126 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 751 and after the incident was 674 with a difference of -77 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Metabase and their customers.
On 03 August 2024, Metabase disclosed Zero-Day Exploit issues under the banner "Critical Zero-Day Exploit in Metabase Grants Attackers Full Admin Access".
Metabase, a popular open-source business intelligence and data visualization platform, has confirmed active exploitation of a critical zero-day vulnerability (GHSA-vwf4-m7j8-wcjf) allowing unauthenticated attackers to gain full administrator control of affected instances.
The disruption is felt across the environment, affecting Metabase instances (versions 0.58 through 0.63), and exposing Customer information (names, addresses, phone numbers, emails), stored credentials, connected database access.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Patch released (versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, 0.63.5), and began remediation that includes Revoke active sessions, audit API keys, review admin accounts, rotate database credentials, inspect logs for unauthorized activity.
The case underscores how Ongoing, and recommending next steps like Self-hosted users should patch immediately to versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, or 0.63.5. Revoke active sessions, audit API keys, review admin accounts, rotate database credentials, and inspect logs for unauthorized activity.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (95%), supported by evidence indicating critical zero-day vulnerability in publicly accessible *POST /api/session/reset_password* endpoint. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: SQL (T1059.001) with high confidence (90%), supported by evidence indicating attackers can inject arbitrary SQL commands into Metabase’s database. Under the Privilege Escalation tactic, the analysis identified Valid Accounts: Local Accounts (T1078.003) with high confidence (90%), supported by evidence indicating escalate privileges to an admin account via SQL injection. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with moderate to high confidence (85%), supported by evidence indicating extract stored credentials from Metabase’s database. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating access connected databases and exfiltrate sensitive data. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating data breaches reported with customer information exfiltrated. Under the Defense Evasion tactic, the analysis identified Valid Accounts: Local Accounts (T1078.003) with moderate to high confidence (85%), supported by evidence indicating hijack admin sessions via *GET /api/user/current* (200 status). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Metabase Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/metabase/incident/MET1786299845
- Metabase CyberSecurity Rating page: https://www.rankiteo.com/company/metabase
- Metabase Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/met1786299845-metabase-vulnerability-august-2026/
- Metabase CyberSecurity Score History: https://www.rankiteo.com/company/metabase/history
- Metabase CyberSecurity Incident Source: https://cybersecuritynews.com/metabase-0-day-vulnerability/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf