dbcve.org
GrafanaApplication

CVE-2025-12141

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-15
Fix available
A fix is available. Upgrade to after 12.3.0 or later.
See remediation →
71/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
In Grafana's alerting system, users with edit permissions for a contact point, specifically the permissions “alert.notifications:write” or “alert.notifications.receivers:test” that are granted as part of the fixed role "Contact Point Writer", which is part of the basic role Editor - can edit contact points created by other users, modify the endpoint URL to a controlled server. By invoking the test functionality, attackers can capture and extract redacted secure settings, such as authentication credentials for third-party services (e.g., Slack tokens). This leads to unauthorized access and potential compromise of external integrations.

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

In Grafana's alerting system, users with the Editor role (which includes the Contact Point Writer fixed role) can edit contact points created by other users. Attackers with these permissions can modify endpoint URLs to attacker-controlled servers and use the test functionality to capture redacted secure settings like Slack tokens or other API credentials, leading to compromise of external integrations.

MitigationRestrict or remove the 'alert.notifications:write' and 'alert.notifications.receivers:test' permissions from untrusted Editor-role users, or update Grafana to a version where this authorization flaw is corrected.

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
Affected:>= 8.0.0, <= 12.3.0

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
None
Availability
None

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

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

  1. Check Grafana version
    Run 'grafana-server -v' or check the /api/health endpoint, or look at the UI footer which displays the version
    Affected if Version is between 8.0.0 and 12.3.0 inclusive (including pre-12.3.0 releases like 12.2.x, 12.1.x, 12.0.x, etc.)
  2. Verify alerting is enabled
    Check configuration file (grafana.ini) for '[unified_alerting].[enabled]' set to 'true', or check via API: GET /api/alerting/config
    Affected if Unified alerting is enabled (this is the default in affected versions)
  3. Identify users with Editor role or Contact Point Writer fixed role
    Query API: GET /api/access-control/users/roles or check via UI: Administration > Users > Role mapping shows fixed roles
    Affected if Any user has Editor role or the 'alert.notifications:write' or 'alert.notifications.receivers:test' permissions assigned
  4. Review existing contact points
    Query API: GET /api/v1/notifications/receivers or check via UI: Alerting > Contact points
    Affected if Contact points exist that may contain sensitive API tokens or webhook URLs (especially Slack, PagerDuty, email SMTP, custom webhooks)
  5. Check for recent contact point modifications or test executions
    Review Grafana logs for requests to /api/v1/notifications/receivers/test or POST /api/v1/notifications/receivers, and audit logs for 'test' actions
    Affected if Unusual test executions on contact points by users other than the creator, or modifications to contact points containing sensitive data

A user is affected if running Grafana 8.0.0-12.3.0 with unified alerting enabled and any Editor role or Contact Point Writer users exist who can access contact points containing sensitive credentials.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.3.0
Interim mitigation

Restrict or remove the 'alert.notifications:write' and 'alert.notifications.receivers:test' permissions from untrusted Editor-role users, or update Grafana to a version where this authorization flaw is corrected.

Recommended fix High confidence

Grafana 12.3.1 or later

  1. Upgrade Grafana to version 12.3.1 or later
  2. After upgrading, verify that users with Editor role no longer have the ability to modify contact points created by other users
  3. Test the contact point test functionality to confirm secure settings remain properly redacted
Caveat Review release notes for any breaking changes between your current version and 12.3.1; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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