GrafanaApplication
CVE-2022-39307
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGrafana 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Grafana forgot password endpoint (/api/user/password/sent-reset-email) returns different HTTP responses for existing vs. non-existing user accounts. When a username or email does not exist, the API returns a JSON 'user not found' message, allowing unauthenticated attackers to enumerate valid usernames/emails via the password reset function.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GrafanaApplication
< 8.5.15>= 9.0.0, < 9.2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Grafana versionRun `grafana-server --version` or check the version in the Grafana UI under Server Admin > Stats, or query the /api/health endpointAffected if The version is less than 8.5.15, or greater than or equal to 9.0.0 but less than 9.2.4
-
Verify the forgot password API is accessibleSend a POST request to your-grafana-host/api/user/password/sent-reset-email with a JSON body containing a test username or email, for example: `{"loginOrEmail": "testuser"}`Affected if The endpoint responds with an HTTP 200 or 400 without requiring authentication
-
Confirm response difference for non-existent usersSend a request with a clearly non-existent email (such as `[email protected]`) and note the HTTP status code and response bodyAffected if The response explicitly states 'user not found' or similar message indicating the account does not exist
-
Compare response for potentially existing usersSend requests with common usernames or emails that may exist in your organization and observe if the response differs from the non-existent user caseAffected if The response for a real account differs (for example, returns a generic 'reset email sent' message) from the response for a non-existent account, confirming user enumeration is possible
You are affected if your Grafana version falls within the vulnerable range and the /api/user/password/sent-reset-email endpoint returns distinct messages for existing versus non-existing accounts, allowing an attacker to enumerate valid user accounts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.5.159.2.4
Update Grafana to version 9.2.4 or 8.5.15 (or later patched versions) to remediate this information disclosure vulnerability.
Grafana 8.5.15 or 9.2.4 (or later)
- Upgrade Grafana to version 8.5.15 or later for the 8.x release line
- OR upgrade Grafana to version 9.2.4 or later for the 9.x release line
- Verify the upgrade by testing the password reset functionality at /api/user/password/sent-reset-email to confirm no user enumeration information is leaked
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Grafana
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39307 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data