Most recent entries from all

bdu:2024-02816

2026-10-04T17:57:20.862509+00:00

bdu:2024-02816

BIT-grafana-2023-6152

2026-10-04T17:57:20.862546+00:00

Affected: Bitnami: grafana

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.

certfr-2024-avi-0132 — Une vulnérabilité a été découverte dans Grafana. Elles permettent à un attaquant de provoquer un contournement de la po…

2026-10-04T17:57:20.862580+00:00

certfr-2024-avi-0132

EUVD-2026-217786

2026-10-04T17:57:20.862597+00:00

EUVD-2026-217786

fkie_cve-2023-6152

2026-10-04T17:57:20.862608+00:00

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.

GHSA-3hv4-r2fm-h27f — Email Validation Bypass And Preventing Sign Up From Email's Owner

2026-10-04T17:57:20.862629+00:00

Affected: Go: github.com/grafana/grafana

### 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) * Warn…

gsd-2023-6152

2026-10-04T17:57:20.862689+00:00

gsd-2023-6152

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

2026-10-04T17:57:20.862702+00:00

grafana-10.1.7-1.1 on GA media

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

2026-10-04T17:57:20.862718+00:00

Security Beta update for SUSE Manager Client Tools

UBUNTU-CVE-2023-6152

2026-10-04T17:57:20.862733+00:00

Affected: Ubuntu:16.04:LTS: grafana

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.

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

2026-10-04T17:57:20.862750+00:00

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Grafana ausnutzen, um Sicherheitsvorkehrungen zu umgehen.