The dashboard permissions API does not verify the target dashboard scope and only checks the dashboards.permissions:* action. As a result, a user who has permission management rights on one dashboard can read and modify permissions on other dashboards. This is an organization‑internal privilege escalation.
Security readout for executives and security teams
Plain-English summary
This Grafana issue could let an internal user with permission-management rights on one dashboard change permissions on other dashboards. That can expose sensitive dashboards or grant unauthorized access. The CVSS score is high, but provided sources do not show active exploitation.
Executive priority
Prioritize this for Grafana deployments with delegated dashboard administration or sensitive operational dashboards. Business impact is unauthorized access or permission changes inside the organization, not public unauthenticated compromise based on provided evidence.
Technical view
The dashboard permissions API checks for dashboards.permissions:* but does not verify the target dashboard scope. A low-privileged authenticated user with permission-management rights on one dashboard may read or modify permissions for other dashboards. The issue maps to CWE-639 and CWE-863 and is scored CVSS 8.1.
Likely exposure
Grafana OSS and Enterprise environments using dashboard permission delegation are most relevant. The bundle names versions 10.2.0 and 12.0.0 through 12.3.0, but also marks entries as default unaffected. Treat exact affected status as requiring vendor confirmation.
Exploitation context
Exploitation is organization-internal and requires an authenticated user with dashboard permission-management rights. It is network-reachable, low complexity, and needs no user interaction. No KEV listing or cited source in the bundle indicates active exploitation.
Researcher notes
The core weakness is missing object-scope authorization on dashboard permission API targets. The provided version data is internally inconsistent, so do not rely on the bundle alone for affected/fixed ranges. Use vendor advisory and Red Hat errata for final applicability.
Mitigation direction
Review the Grafana security advisory for affected and fixed version details.
Apply Grafana or Red Hat updates if your deployment is covered by listed advisories.
Temporarily limit dashboard permission-management rights to trusted administrators.
Audit dashboard permission changes for unexpected cross-dashboard modifications.
Check applicable Red Hat errata if using Red Hat-packaged Grafana components.
Validation and detection
Inventory Grafana OSS and Enterprise versions in production and internal environments.
Identify users or service accounts with dashboards.permissions:* rights.
Confirm whether those rights are scoped only to intended dashboards.
Review Grafana logs for unusual dashboard permission reads or changes.
Validate remediation against Grafana and Red Hat advisory guidance.
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 · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
CWE-863: 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.
2CVSS vectors
5Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.