GrafanaApplication
CVE-2021-28147
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 · uneditedThe team sync HTTP API in Grafana Enterprise 6.x before 6.7.6, 7.x before 7.3.10, and 7.4.x before 7.4.5 has an Incorrect Access Control issue. On Grafana instances using an external authentication service and having the EditorsCanAdmin feature enabled, this vulnerability allows any authenticated user to add external groups to any existing team. This can be used to grant a user team permissions that the user isn't supposed to have.
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 confidenceThe team sync HTTP API in Grafana Enterprise contains an incorrect access control vulnerability. When an instance uses external authentication (such as LDAP or OAuth) and has the EditorsCanAdmin feature enabled, any authenticated user can add external groups to any existing team, bypassing intended permission restrictions and allowing unauthorized privilege escalation.
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
>= 6.0.0, < 6.7.6>= 7.0.0, < 7.3.10>= 7.4.0, < 7.4.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Check Grafana versionRun `grafana-server --version` or check the Grafana UI at /api/health. Compare the version number to the affected ranges: 6.0.0 to 6.7.5, 7.0.0 to 7.3.9, or 7.4.0 to 7.4.4.Affected if The installed version falls within any of the vulnerable ranges (6.0.0 <= version < 6.7.6, 7.0.0 <= version < 7.3.10, or 7.4.0 <= version < 7.4.5)
-
Verify external authentication is enabledInspect the Grafana configuration file (grafana.ini) for [auth.ldap] or [auth.oauth] sections, or check the UI configuration under Configuration > Authentication.Affected if LDAP authentication or OAuth is configured and enabled on the instance
-
Confirm EditorsCanAdmin feature settingInspect grafana.ini for the `editors_can_admin` setting under [users], or query the Grafana HTTP API endpoint GET /api/admin/stats. The default is false.Affected if The configuration has editors_can_admin set to true or enabled
The instance is affected only if all three conditions are true: a vulnerable Grafana version is installed, external authentication (LDAP or OAuth) is enabled, AND the EditorsCanAdmin feature is turned on.
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.
From vendor data6.7.67.3.107.4.5
Upgrade to Grafana Enterprise 6.7.6, 7.3.10, or 7.4.5 or later. If immediate upgrade is not feasible, disable the EditorsCanAdmin feature as a workaround.
Fix this in Grafana
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28147 — 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-2021-28147 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