An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard. The user must have write access to the dashboard to escalate privilege.
Security readout for executives and security teams
Plain-English summary
A Grafana flaw lets a user with Editor permissions overwrite a dashboard they can already edit and end up as the admin of that dashboard. It does not give them control of the whole Grafana server, but it does let them change who can access or modify that dashboard going forward.
Executive priority
Prioritize patching within the standard high-severity SLA. Business risk centers on dashboard integrity and access-control drift rather than data theft or outage, but rushed insider misuse in analytics-critical teams justifies prompt action.
Technical view
Grafana's dashboard import path fails to properly enforce ACLs (CWE-284) when an Editor overwrites an existing dashboard they have write access to. The overwrite replaces permissions so the acting user becomes dashboard admin. CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N) reflects low-privilege network access with high integrity impact scoped to the affected dashboard.
Likely exposure
Organizations running Grafana OSS across the version ranges listed in the vendor advisory (spanning 8.5.0 through 13.0.1 branches) where Editor-role users share workspaces with dashboards owned by higher-privileged users. Internet-exposed or multi-tenant Grafana instances raise exposure.
Exploitation context
No CISA KEV listing and no public evidence of active exploitation in the provided sources. Exploitation requires an authenticated Editor account that already has write access to a target dashboard, so the attacker must be an insider or have compromised Editor credentials.
Researcher notes
CWE-284 with S:U indicates the escalation is contained to the individual dashboard, not the Grafana server or org. The bug hinges on the overwrite path resetting ACLs. Verify whether folder-level permissions also propagate, and confirm exact fixed versions from the Grafana advisory since the affected list spans multiple release branches.
Mitigation direction
Upgrade Grafana OSS to a fixed release per the vendor security advisory.
Review Editor-role assignments and remove access from users who do not need it.
Audit dashboard-level permissions on sensitive dashboards and tighten write access.
Restrict Grafana admin/UI exposure to trusted networks or SSO-gated access.
Enable and monitor Grafana audit logs for dashboard import and permission changes.
Validation and detection
Inventory Grafana OSS instances and compare versions against the vendor advisory.
Confirm patched build is running via the Grafana /api/health or version banner post-upgrade.
Test that an Editor overwriting a shared dashboard no longer becomes its admin.
Review recent dashboard permission changes in audit logs for anomalies.
Verify least-privilege role assignments across Grafana organizations and folders.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.