# CVE-2022-43776: Server-side request forgery in Metabase

> Attackers can exploit the url parameter in the geojson endpoint to perform Server Side Request Forgery, bypassing previous blacklist protections via redirects.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-mppc-g8x5-rq8c

## What is CVE-2022-43776?

CVE-2022-43776 is a medium-severity server-side request forgery vulnerability in Metabase, published on 26 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The url parameter of the /api/geojson endpoint in Metabase versions <44.5 can be used to perform Server Side Request Forgery attacks. Previously implemented blacklists could be circumvented by leveraging 301 and 302 redirects.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-43776?

It affects 1 product.


Products: Metabase Metabase.

## How do I fix CVE-2022-43776?

No fix has been published for CVE-2022-43776 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-43776 being exploited?

There is no known exploitation of CVE-2022-43776 in the wild and no public exploit code.

## Other vulnerabilities in Metabase

- [CVE-2026-72898](https://insights.sbomify.com/CVE-2026-72898/): Metabase SQL Injection (critical 10.0, exploited in the wild)
- [CVE-2021-41277](https://insights.sbomify.com/CVE-2021-41277/): Metabase GeoJSON API Local File Inclusion (critical 10.0, exploited in the wild)
- [CVE-2026-50148](https://insights.sbomify.com/CVE-2026-50148/): Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write (critical 10.0)
- [CVE-2023-37470](https://insights.sbomify.com/CVE-2023-37470/): Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint (critical 10.0)
- [CVE-2026-59827](https://insights.sbomify.com/CVE-2026-59827/): Metabase: Unsafe Deserialization of H2 Query Results (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43776 and fix it if it is affected.

What it is: CVE-2022-43776 is a medium-severity server-side request forgery vulnerability in Metabase, published on 26 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43776 in the wild and no public exploit code.

Affected product: Metabase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-43776/ (Markdown: https://insights.sbomify.com/CVE-2022-43776/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-43776
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-43776
- OSV: https://osv.dev/vulnerability/CVE-2022-43776

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-43776/
Summaries are generated and may contain mistakes; the official description above is the record.