# CVE-2023-2183: Grafana has Broken Access Control in Alert manager: Viewer can send test alerts > Attackers with Viewer role can bypass UI restrictions to send test alerts via API, enabling spam or phishing attacks. - **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 6 Jun 2023 - **Updated:** 13 Feb 2025 - **Also known as:** BIT-grafana-2023-2183, GHSA-cvm3-pp2j-chr3, UBUNTU-CVE-2023-2183 ## What is CVE-2023-2183? CVE-2023-2183 is a medium-severity missing authorization vulnerability in Grafana Grafana, published on 6 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Grafana is an open-source platform for monitoring and observability. The option to send a test alert is not available from the user panel UI for users having the Viewer role. It is still possible for a user with the Viewer role to send a test alert using the API as the API does not check access to this function. This might enable malicious users to abuse the functionality by sending multiple alert messages to e-mail and Slack, spamming users, prepare Phishing attack or block SMTP server. Users may upgrade to version 9.5.3, 9.4.12, 9.3.15, 9.2.19 and 8.5.26 to receive a fix. Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2023-2183? 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 | All versions | 8.5.26 | | `github.com/grafana/grafana` | Go | All versions | 8.5.26 | | `github.com/grafana/grafana` | Go | From 9.0.0 | 9.2.19 | | `github.com/grafana/grafana` | Go | From 9.0.0 | 9.2.19 | | `github.com/grafana/grafana` | Go | From 9.3.0 | 9.3.15 | | `github.com/grafana/grafana` | Go | From 9.3.0 | 9.3.15 | | `github.com/grafana/grafana` | Go | From 9.4.0 | 9.4.12 | | `github.com/grafana/grafana` | Go | From 9.4.0 | 9.4.12 | | `github.com/grafana/grafana` | Go | From 9.5.0 | 9.5.3 | | `github.com/grafana/grafana` | Go | From 9.5.0 | 9.5.3 | | `grafana` | Bitnami | From 8.0.0 | 8.5.26, 9.2.19, 9.3.15, 9.4.12, 9.5.3 | Products: Grafana Grafana. ## How do I fix CVE-2023-2183? Upgrade github.com/grafana/grafana to a fixed version for your release line: 8.5.26, 9.2.19, 9.3.15 or 9.4.12. ## Is CVE-2023-2183 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2183 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-2183 and fix it if it is affected. What it is: CVE-2023-2183 is a medium-severity missing authorization vulnerability in Grafana Grafana, published on 6 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2183 exists. Affected packages and fixed versions: - github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.26 - github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.26 - github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.2.19 - github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.2.19 - github.com/grafana/grafana (Go): affected from 9.3.0; fixed in 9.3.15 - github.com/grafana/grafana (Go): affected from 9.3.0; fixed in 9.3.15 - github.com/grafana/grafana (Go): affected from 9.4.0; fixed in 9.4.12 - github.com/grafana/grafana (Go): affected from 9.4.0; fixed in 9.4.12 - github.com/grafana/grafana (Go): affected from 9.5.0; fixed in 9.5.3 - github.com/grafana/grafana (Go): affected from 9.5.0; fixed in 9.5.3 - grafana (Bitnami): affected from 8.0.0; fixed in 8.5.26, 9.2.19, 9.3.15, 9.4.12, 9.5.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-2183/ (Markdown: https://insights.sbomify.com/CVE-2023-2183/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-2183 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-2183 - OSV: https://osv.dev/vulnerability/CVE-2023-2183 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-2183/ Summaries are generated and may contain mistakes; the official description above is the record.