Threats / Metabase / CVE-2021-41277
CVE-2021-41277
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Metabase vulnerability
Metabase contains a local file inclusion vulnerability in custom map support via the GeoJSON API endpoint, allowing unauthorized file access.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit the custom map GeoJSON API to read arbitrary files from the server filesystem, exposing sensitive configuration, credentials, and application data without authentication.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
656 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-12).
Probability (EPSS)
EPSS 0.96887 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Metabase, Metabase. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-200 Information Exposure — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify the Metabase custom map API endpoint accepts GeoJSON file paths without proper validation.
Business
Attacker gains reconnaissance capability to map the application's file structure and locate sensitive data stores.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft requests to the API specifying file paths outside the intended GeoJSON directory using path traversal techniques.
Business
Sensitive files including database credentials, API keys, and configuration become accessible to the attacker.
3
Lateral reach — past segmentation narrative 3
Attacker
I extract credentials and secrets from readable configuration files and application data.
Business
Compromised credentials enable lateral movement to databases, external services, and downstream systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05