{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-30371 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30371 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30371 is a low-severity server-side request forgery vulnerability in metabase, published on 28 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-30371 and fix it if it is affected.\n\nWhat it is: CVE-2025-30371 is a low-severity server-side request forgery vulnerability in metabase, published on 28 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-30371 in the wild and no public exploit code.\n\nAffected product: metabase. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-30371/ (Markdown: https://insights.sbomify.com/CVE-2025-30371/index.md)","id":"CVE-2025-30371","markdown":"https://insights.sbomify.com/CVE-2025-30371/index.md","name":"CVE-2025-30371","record":{"aliases":["GHSA-8xf9-9jc8-qp98"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Metabase BI tool","requires_auth":"high_privilege","summary":"Attackers can bypass local link protections in the GeoJson endpoint to access internal resources, impacting self-hosted Metabase instances.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Metabase is a business intelligence and embedded analytics tool. Versions prior to v0.52.16.4, v1.52.16.4, v0.53.8, and v1.53.8 are vulnerable to circumvention of local link access protection in GeoJson endpoint. Self hosted Metabase instances that are using the GeoJson feature could be potentially impacted if their Metabase is colocated with other unsecured resources. This is fixed in v0.52.16.4, v1.52.16.4, v0.53.8, and v1.53.8. Migrating to Metabase Cloud or redeploying Metabase in a dedicated subnet with strict outbound port controls is an available workaround.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Metabase vulnerable to circumvention of local link access protection in GeoJson endpoint","id":"CVE-2025-30371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Emlog Pro contains an SQL injection vulnerability.","id":"CVE-2025-30372"},"packages":[],"prev":{"headline":"jupyterlab-git has a command injection vulnerability in \"Open Git Repository in Terminal\"","id":"CVE-2025-30370"},"products":["metabase"],"published":"2025-03-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-28","vendors":["metabase"]},"summary":"Attackers can bypass local link protections in the GeoJson endpoint to access internal resources, impacting self-hosted Metabase instances.","url":"https://insights.sbomify.com/CVE-2025-30371/"}