dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-3260

HIGH · 8.3 CVSS v3.1 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A security vulnerability in the /apis/dashboard.grafana.app/* endpoints allows authenticated users to bypass dashboard and folder permissions. The vulnerability affects all API versions (v0alpha1, v1alpha1, v2alpha1). Impact: - Viewers can view all dashboards/folders regardless of permissions - Editors can view/edit/delete all dashboards/folders regardless of permissions - Editors can create dashboards in any folder regardless of permissions - Anonymous users with viewer/editor roles are similarly affected Organization isolation boundaries remain intact. The vulnerability only affects dashboard access and does not grant access to datasources.

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 confidence

This is a broken access control vulnerability in Grafana's dashboard API endpoints (/apis/dashboard.grafana.app/*) where proper permission validation is bypassed, allowing authenticated users to access, modify, or delete dashboards and folders outside their assigned role permissions.

MitigationApply vendor-supplied patches/updates to Grafana that fix the authorization bypass in dashboard API endpoints; verify that role-based access controls are properly enforced after updating.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana version
    Check your installed Grafana version by running `grafana-server --version` or inspecting the grafana metadata (e.g., in Docker labels, package manager, or the /api/health endpoint)
    Affected if The installed version falls within the vulnerable range (prior to the security patch) and has not been updated to include the CVE-2025-3260 fix
  2. Confirm dashboard API is in use
    Check if the Grafana instance uses the unified storage dashboard API by reviewing configuration files (grafana.ini), checking for the presence of the /apis/dashboard.grafana.app/* endpoints, or inspecting API documentation for dashboard provisioning
    Affected if The dashboard API endpoints (v0alpha1, v1alpha1, v2alpha1) are exposed or enabled in the Grafana deployment
  3. Inspect API authorization configuration
    Review Grafana role-based access control (RBAC) settings in grafana.ini under [auth] and [users] sections, and verify that the dashboard API has authorization middleware configured by examining the API response headers or checking the grafana logs for authorization enforcement
    Affected if The dashboard API endpoints lack proper authorization middleware or RBAC enforcement is disabled for the dashboard API routes
  4. Test API permission enforcement
    Create a test user with limited viewer or editor role, then attempt to access a dashboard or folder they should NOT have permission to via the /apis/dashboard.grafana.app/* endpoints using curl or a REST client (e.g., GET /apis/dashboard.grafana.app/v0alpha1/namespaces/default/dashboards/{unauthorized-dashboard-id})
    Affected if The authenticated user without permissions can successfully retrieve, modify, or delete dashboards or folders they should not have access to through the API, indicating the authorization bypass is present

A user is affected if they run a Grafana version prior to the CVE-2025-3260 patch, have the dashboard API endpoints enabled, and the authorization bypass allows authenticated users to access dashboards or folders outside their assigned permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches/updates to Grafana that fix the authorization bypass in dashboard API endpoints; verify that role-based access controls are properly enforced after updating.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3260 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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