GrafanaApplication
CVE-2023-4822
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGrafana is an open-source platform for monitoring and observability. The vulnerability impacts Grafana instances with several organizations, and allows a user with Organization Admin permissions in one organization to change the permissions associated with Organization Viewer, Organization Editor and Organization Admin roles in all organizations. It also allows an Organization Admin to assign or revoke any permissions that they have to any user globally. This means that any Organization Admin can elevate their own permissions in any organization that they are already a member of, or elevate or restrict the permissions of any other user. The vulnerability does not allow a user to become a member of an organization that they are not already a member of, or to add any other users to an organization that the current user is not a member of.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInsecure permission handling in Grafana's multi-organization feature allows an Organization Admin in one organization to modify role permissions (Viewer, Editor, Admin) across ALL organizations, and to assign or revoke their own permissions to any other user globally. This is a privilege escalation vulnerability where insufficient authorization checks permit cross-organization permission manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GrafanaApplication
>= 8.0.0, < 9.4.16>= 9.5.0, < 9.5.11>= 10.0.0, < 10.0.7>= 10.1.0, < 10.1.3= 10.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Grafana versionRun 'grafana-server -v' or check the Grafana UI at Administration > Stats (or via API: GET /api/health)Affected if The installed version falls within >= 8.0.0 and < 9.4.16, OR >= 9.5.0 and < 9.5.11, OR >= 10.0.0 and < 10.0.7, OR >= 10.1.0 and < 10.1.3, OR equals 10.1.4
-
Determine if multi-organization feature is enabledCheck grafana.ini configuration file for 'multi_organization = true' setting under [users] section, or query the API: GET /api/orgAffected if Multi-organization is enabled and multiple organizations exist beyond the default primary organization
-
List Organization Admin role assignmentsQuery Grafana API: GET /api/orgs/<orgId>/users to list members and their roles, or check via UI under Organization > Members for each organizationAffected if Any user holds the Organization Admin role in an organization other than the primary one
-
Audit permission modifications across organizationsReview Grafana logs for API calls to PUT /api/orgs/{orgId}/users/{userId}/roles or examine audit logs for role permission changes
You are affected if your Grafana version is within the affected ranges AND multi-organization feature is enabled with more than one organization present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.4.169.5.1110.0.7
Apply the vendor-released patch/update for Grafana. Until patched, strictly limit Organization Admin role assignments to trusted personnel and implement monitoring for unauthorized permission modifications.
Upgrade to Grafana 9.4.16, 9.5.11, 10.0.7, 10.1.3, or the latest stable 10.x release (10.2.0+)
- 1. Identify the currently installed Grafana version using `grafana-server --version` or checking the Grafana admin UI status page
- 2. For Grafana 8.x versions (>=8.0.0): upgrade to Grafana 9.4.16 or later (preferably 9.5.x or 10.x for latest features and security fixes)
- 3. For Grafana 9.5.x versions: upgrade to Grafana 9.5.11 or later
- 4. For Grafana 10.0.x versions: upgrade to Grafana 10.0.7 or later
- 5. For Grafana 10.1.x versions: upgrade to Grafana 10.1.3 or later
- 6. After upgrade, verify the Grafana service is running: `systemctl status grafana-server` or `docker ps` if using containers
- 7. Test that user permissions and organization roles function correctly after the upgrade
- 8. Review audit logs to confirm no unauthorized permission changes occurred during the vulnerable period
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Grafana
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-4822 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data