Improper Access ControlWeakness · CWE-284

CVE-2025-3580

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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
An access control vulnerability was discovered in Grafana OSS where an Organization administrator could permanently delete the Server administrator account. This vulnerability exists in the DELETE /api/org/users/ endpoint. The vulnerability can be exploited when: 1. An Organization administrator exists 2. The Server administrator is either: - Not part of any organization, or - Part of the same organization as the Organization administrator Impact: - Organization administrators can permanently delete Server administrator accounts - If the only Server administrator is deleted, the Grafana instance becomes unmanageable - No super-user permissions remain in the system - Affects all users, organizations, and teams managed in the instance The vulnerability is particularly serious as it can lead to a complete loss of administrative control over the Grafana instance.

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

An access control flaw in Grafana OSS allows an Organization administrator to delete the Server administrator account via the DELETE /api/org/users/ endpoint. The vulnerability occurs because the endpoint does not properly verify that the requesting user lacks permission to remove the highest-privilege administrative account, enabling org admins to permanently delete server admins when the server admin is either unassigned to any organization or shares the same organization.

MitigationImplement authorization checks in the DELETE /api/org/users/ endpoint to prevent Organization administrators from deleting Server administrator accounts, regardless of organization membership. Until a patch is applied, limit the creation of Organization administrators and monitor for unauthorized admin account deletion.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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 checks

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

  1. Confirm Grafana OSS version
    Query the Grafana instance for its version using the /api/health endpoint or check the grafana-server process/package version
    Affected if The installed version is any Grafana OSS version that has the DELETE /api/org/users/ endpoint and contains Organization Administrator and Server Administrator role types
  2. Identify Organization Administrator accounts
    Query the Grafana API using an authenticated session with admin privileges to list users with Organization Administrator role: GET /api/org/users/ or inspect user role assignments in Grafana's user administration interface
    Affected if There exists at least one user granted the Organization Administrator role in any organization
  3. Identify Server Administrator accounts
    Query Grafana's user administration for users with Server Admin role: GET /api/admin/users/ or inspect Grafana's server user administration panel
    Affected if There exists at least one user granted the Server Administrator role, particularly if that server admin is either unassigned to any organization or shares an organization with an Organization Administrator
  4. Review audit logs for deletion events
    Inspect Grafana's audit logs or logs for HTTP DELETE requests to /api/org/users/ endpoint. Check logs for events where an Organization Administrator may have removed a user
    Affected if Audit logs show DELETE /api/org/users/ calls that resulted in removal of a Server Administrator account, or logs indicate such deletions have occurred in the past

Your environment is affected if you run a Grafana OSS version with the DELETE /api/org/users/ endpoint and have both Organization Administrator accounts and Server Administrator accounts where the server admin is either organization-unassigned or shares an organization with an org admin.

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

Implement authorization checks in the DELETE /api/org/users/ endpoint to prevent Organization administrators from deleting Server administrator accounts, regardless of organization membership. Until a patch is applied, limit the creation of Organization administrators and monitor for unauthorized admin account deletion.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3580 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3580 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