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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-6152: 1.39% estimated exploitation activity in the next 30 days; percentile 72.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 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. 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,…

Published by the source

13 Feb 2024, 22:25 UTC

Last modified by the source

18 Feb 2025, 22:29 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3hv4-r2fm-h27f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-6152

Advisory: Email Validation Bypass And Preventing Sign Up From Email's Owner
IDs: CVE-2023-6152, GHSA-3hv4-r2fm-h27f
Record: https://patchnext.com/advisories/cve-2023-6152 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/grafana 10.3.3, 10.2.4, 10.1.7, 10.0.11, 9.5.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/grafana: affected >= 2.5.0, < 9.5.16; >= 10.0.0, < 10.0.11; >= 10.1.0, < 10.1.7; >= 10.2.0, < 10.2.4; >= 10.3.0, < 10.3.3; fixed in 10.1.7, 10.0.11, 9.5.16, 10.3.3, 10.2.4

## Suggested inspection (read-only)
- Go github.com/grafana/grafana: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/grafana/grafana.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3hv4-r2fm-h27f (GitHub-reviewed advisory GHSA-3hv4-r2fm-h27f lists affected ranges: Go github.com/grafana/grafana >=2.5.0 =10.0.0 =10.1.0 =10.2.0 =10.3.0 <10.3.3)

Commands are suggestions: review each one before running it.