# CVE-2022-39307: Grafana subject to Exposure of Sensitive Information resulting in User enumeration via forget password

> Unauthenticated attackers can enumerate valid usernames via distinct error messages in the password reset feature, exposing sensitive user information.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L`)
- **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:** 9 Nov 2022
- **Updated:** 28 Jan 2026
- **Also known as:** BIT-grafana-2022-39307, CLSA-2025-1758135826, GHSA-3p62-42x7-gxg5, GO-2024-2844, MINI-27mr-mq94-742x, MINI-354v-vh2v-q2xw, MINI-48cg-fvm3-7r99, MINI-7fxh-hj3w-qj86, MINI-ch3r-f3fc-ff6f, MINI-gcvm-mp95-w8c2, MINI-gj7c-6w99-v599, MINI-hrxr-9467-jfmv, MINI-jq4r-pfh9-qvrm, MINI-mqh7-c9hq-hxwx, MINI-q88r-6944-6g95, MINI-q8cv-8p97-j2r8, MINI-qgrp-w2hf-xcvm, MINI-r897-c96m-29vf, MINI-rpvw-4c7m-qfgx, MINI-x6gr-fcrh-pvvv, MINI-xm8g-cfxw-wmxh, UBUNTU-CVE-2022-39307

## What is CVE-2022-39307?

CVE-2022-39307 is a medium-severity vulnerability in Grafana Grafana, published on 9 Nov 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. When using the forget password on the login page, a POST request is made to the `/api/user/password/sent-reset-email` URL. When the username or email does not exist, a JSON response contains a “user not found” message. This leaks information to unauthenticated users and introduces a security risk. This issue has been patched in 9.2.4 and backported to 8.5.15. There are no known workarounds.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

6 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | All versions | None |
| `github.com/grafana/grafana` | Go | All versions | 8.5.15 |
| `github.com/grafana/grafana` | Go | All versions | 8.5.15 |
| `github.com/grafana/grafana` | Go | From 9.0.0 | 9.2.4 |
| `github.com/grafana/grafana` | Go | From 9.0.0 | 9.2.4 |
| `grafana` | Bitnami | All versions | 8.5.15, 9.2.4 |

Products: Grafana Grafana.

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

Upgrade github.com/grafana/grafana to a fixed version for your release line: 8.5.15 or 9.2.4.

## Is CVE-2022-39307 being exploited?

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

## Other vulnerabilities in Grafana Grafana

- [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild)
- [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0)
- [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8)
- [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39307 is a medium-severity vulnerability in Grafana Grafana, published on 9 Nov 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-39307 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected all versions; no fix listed
- github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.15
- github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.15
- github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.2.4
- github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.2.4
- grafana (Bitnami): affected all versions; fixed in 8.5.15, 9.2.4

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

## Sources

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

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