dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-6023

HIGH · 7.6 CVSS v3.1 Published 2025-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

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 open redirect vulnerability has been identified in Grafana OSS that can be exploited to achieve XSS attacks. The vulnerability was introduced in Grafana v11.5.0. The open redirect can be chained with path traversal vulnerabilities to achieve XSS. Fixed in versions 12.0.2+security-01, 11.6.3+security-01, 11.5.6+security-01, 11.4.6+security-01 and 11.3.8+security-01

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 open redirect vulnerability in Grafana OSS allows attackers to craft malicious URLs that redirect users to attacker-controlled sites. When combined with path traversal vulnerabilities, this can be chained to achieve cross-site scripting (XSS) attacks. The vulnerability was introduced in Grafana v11.5.0 and affects the OSS edition.

MitigationUpgrade Grafana to version 12.0.2+security-01, 11.6.3+security-01, 11.5.6+security-01, 11.4.6+security-01, or 11.3.8+security-01 (or later) to remediate this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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. Check installed Grafana version
    Run `grafana-server -v` or check the Grafana UI: hover over the Grafana icon in the bottom left to see the version number. Alternatively, query the API at `http://<your-grafana>/api/health`
    Affected if Version is 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.6.0, 11.6.1, 11.6.2, 11.3.0 through 11.3.7, or any version 11.7.0 through 11.9.x through 11.9.1, or any version 12.0.0 through 12.0.1 (i.e., any version >= 11.5.0 but below the fixed releases)
  2. Confirm Grafana edition is OSS
    Check the Grafana UI: hover over the Grafana icon in the bottom left - it will show 'Grafana OSS' or 'Grafana Enterprise'. Or check the startup logs for 'Grafana edition: open source'
    Affected if Edition shows 'Grafana OSS' (Enterprise edition is not affected by this CVE)
  3. Inspect redirect-enabled endpoints
    Review Grafana configuration file (grafana.ini) for any custom URL redirect or whitelist settings under [security] or [auth] sections. Also check for any proxy or reverse proxy configurations that may handle redirects
    Affected if Custom redirect configurations exist that could allow external URLs to be passed as redirect targets
  4. Check for exposed Grafana URLs
    Review access logs for patterns like `GET /login?redirect=`, `GET /?redirect=`, or similar redirect parameters pointing to external domains. Search for 'http://' or 'https://' in redirect parameter values
    Affected if Requests show redirect parameters being used with external/untrusted URLs

You are affected if you run Grafana OSS version 11.5.0 or higher (and below the fixed versions) and users can access Grafana login or authenticated pages with redirect parameters.

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

Upgrade Grafana to version 12.0.2+security-01, 11.6.3+security-01, 11.5.6+security-01, 11.4.6+security-01, or 11.3.8+security-01 (or later) to remediate this vulnerability.

Recommended fix High confidence

11.3.8+security-01, 11.4.6+security-01, 11.5.6+security-01, 11.6.3+security-01, or 12.0.2+security-01 (choose based on current release line)

  1. Identify the current Grafana version by checking the Grafana web UI (Settings > About) or running 'grafana-server -v'
  2. Determine which release line the current version belongs to (v11.3.x, v11.4.x, v11.5.x, v11.6.x, or v12.x)
  3. Plan the upgrade to the appropriate fixed version for that release line
  4. For Grafana v11.3.x: upgrade to 11.3.8+security-01 or later
  5. For Grafana v11.4.x: upgrade to 11.4.6+security-01 or later
  6. For Grafana v11.5.x: upgrade to 11.5.6+security-01 or later
  7. For Grafana v11.6.x: upgrade to 11.6.3+security-01 or later
  8. For Grafana v12.x: upgrade to 12.0.2+security-01 or later
Caveat Standard Grafana upgrade considerations apply; review release notes for any deprecation warnings between versions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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