# CVE-2023-6152: Email Validation Bypass And Preventing Sign Up From Email's Owner > Attackers can bypass email verification to change their account email, potentially leading to account takeover in Grafana. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Feb 2024 - **Updated:** 15 Feb 2025 - **Also known as:** BIT-grafana-2023-6152, GHSA-3hv4-r2fm-h27f, SUSE-SU-2024:1419-1, UBUNTU-CVE-2023-6152, openSUSE-SU-2024:13713-1 ## What is CVE-2023-6152? CVE-2023-6152 is a medium-severity vulnerability in Grafana Grafana, published on 13 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2023-6152? 11 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/grafana/grafana` | Go | From 10.0.0 | 10.0.11 | | `github.com/grafana/grafana` | Go | From 10.0.0 | 10.0.11 | | `github.com/grafana/grafana` | Go | From 10.1.0 | 10.1.7 | | `github.com/grafana/grafana` | Go | From 10.1.0 | 10.1.7 | | `github.com/grafana/grafana` | Go | From 10.2.0 | 10.2.4 | | `github.com/grafana/grafana` | Go | From 10.2.0 | 10.2.4 | | `github.com/grafana/grafana` | Go | From 10.3.0 | 10.3.3 | | `github.com/grafana/grafana` | Go | From 10.3.0 | 10.3.3 | | `github.com/grafana/grafana` | Go | From 2.5.0 | 9.5.16 | | `github.com/grafana/grafana` | Go | From 2.5.0 | 9.5.16 | | `grafana` | Bitnami | From 2.5.0 | 9.5.16, 10.0.11, 10.1.7, 10.2.4, 10.3.3 | | `golang-github-prometheus-alertmanager` | SUSE:Manager Client Tools 12-BETA | All versions | 0.26.0-4.18.2 | | `golang-github-prometheus-node_exporter` | SUSE:Manager Client Tools 12-BETA | All versions | 1.7.0-4.18.2 | | `golang-github-prometheus-promu` | SUSE:Manager Client Tools 12-BETA | All versions | 0.14.0-4.15.1 | | `grafana` | SUSE:Manager Client Tools 12-BETA | All versions | 9.5.16-4.27.1 | | `spacecmd` | SUSE:Manager Client Tools 12-BETA | All versions | 5.0.5-41.48.1 | | `spacewalk-client-tools` | SUSE:Manager Client Tools 12-BETA | All versions | 5.0.4-55.51.1 | | `supportutils-plugin-susemanager-client` | SUSE:Manager Client Tools 12-BETA | All versions | 5.0.3-9.21.1 | | `uyuni-tools` | SUSE:Manager Client Tools 12-BETA | All versions | 0.1.7-3.8.1 | | `grafana` | openSUSE:Tumbleweed | All versions | 10.1.7-1.1 | Products: Grafana Grafana. ## How do I fix CVE-2023-6152? Upgrade github.com/grafana/grafana to a fixed version for your release line: 10.0.11, 10.1.7, 10.2.4 or 10.3.3. ## Is CVE-2023-6152 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6152 exists. ## Other vulnerabilities in Grafana Grafana - [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild) - [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0) - [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8) - [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8) - [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-6152 and fix it if it is affected. What it is: CVE-2023-6152 is a medium-severity vulnerability in Grafana Grafana, published on 13 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6152 exists. Affected packages and fixed versions: - github.com/grafana/grafana (Go): affected from 10.0.0; fixed in 10.0.11 - github.com/grafana/grafana (Go): affected from 10.0.0; fixed in 10.0.11 - github.com/grafana/grafana (Go): affected from 10.1.0; fixed in 10.1.7 - github.com/grafana/grafana (Go): affected from 10.1.0; fixed in 10.1.7 - github.com/grafana/grafana (Go): affected from 10.2.0; fixed in 10.2.4 - github.com/grafana/grafana (Go): affected from 10.2.0; fixed in 10.2.4 - github.com/grafana/grafana (Go): affected from 10.3.0; fixed in 10.3.3 - github.com/grafana/grafana (Go): affected from 10.3.0; fixed in 10.3.3 - github.com/grafana/grafana (Go): affected from 2.5.0; fixed in 9.5.16 - github.com/grafana/grafana (Go): affected from 2.5.0; fixed in 9.5.16 - grafana (Bitnami): affected from 2.5.0; fixed in 9.5.16, 10.0.11, 10.1.7, 10.2.4, 10.3.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-6152/ (Markdown: https://insights.sbomify.com/CVE-2023-6152/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6152 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6152 - OSV: https://osv.dev/vulnerability/CVE-2023-6152 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-6152/ Summaries are generated and may contain mistakes; the official description above is the record.