# CVE-2022-21703: Cross Site Request Forgery in Grafana

> Attackers can trick authenticated high-privilege Grafana users into granting them elevated access via cross-site request forgery.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Feb 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-grafana-2022-21703, GHSA-cmf4-h3xc-jw8w, UBUNTU-CVE-2022-21703

## What is CVE-2022-21703?

CVE-2022-21703 is a medium-severity vulnerability in Fedoraproject Fedora, published on 8 Feb 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Grafana is an open-source platform for monitoring and observability. Affected versions are subject to a cross site request forgery vulnerability which allows attackers to elevate their privileges by mounting cross-origin attacks against authenticated high-privilege Grafana users (for example, Editors or Admins). An attacker can exploit this vulnerability for privilege escalation by tricking an authenticated user into inviting the attacker as a new user with high privileges. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

5 open source packages ship an affected version, including github.com/grafana/grafana/pkg/web and grafana. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana/pkg/web` | Go | From 3.0-beta1 | 7.5.15 |
| `github.com/grafana/grafana/pkg/web` | Go | From 3.0-beta1 | 7.5.15 |
| `github.com/grafana/grafana/pkg/web` | Go | From 8.0.0 | 8.3.5 |
| `github.com/grafana/grafana/pkg/web` | Go | From 8.0.0 | 8.3.5 |
| `grafana` | Bitnami | From 3.0.1 | 7.5.15, 8.3.5 |

Products: Fedoraproject Fedora, Grafana Grafana, Netapp E-Series Performance Analyzer.

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

Upgrade github.com/grafana/grafana/pkg/web to a fixed version for your release line: 7.5.15 or 8.3.5.

## Is CVE-2022-21703 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21703 is a medium-severity vulnerability in Fedoraproject Fedora, published on 8 Feb 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-21703 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana/pkg/web (Go): affected from 3.0-beta1; fixed in 7.5.15
- github.com/grafana/grafana/pkg/web (Go): affected from 3.0-beta1; fixed in 7.5.15
- github.com/grafana/grafana/pkg/web (Go): affected from 8.0.0; fixed in 8.3.5
- github.com/grafana/grafana/pkg/web (Go): affected from 8.0.0; fixed in 8.3.5
- grafana (Bitnami): affected from 3.0.1; fixed in 7.5.15, 8.3.5

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-21703/ (Markdown: https://insights.sbomify.com/CVE-2022-21703/index.md)
```

## Sources

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

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