dbcve.org
GrafanaApplication

CVE-2025-4123

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 10.4.18 / 11.2.9 or later.
See remediation →
68/100
Remediation priority · Elevated
High EPSS Public exploit 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
A cross-site scripting (XSS) vulnerability exists in Grafana caused by combining a client path traversal and open redirect. This allows attackers to redirect users to a website that hosts a frontend plugin that will execute arbitrary JavaScript. This vulnerability does not require editor permissions and if anonymous access is enabled, the XSS will work. If the Grafana Image Renderer plugin is installed, it is possible to exploit the open redirect to achieve a full read SSRF. The default Content-Security-Policy (CSP) in Grafana will block the XSS though the `connect-src` directive.

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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:< 10.4.18>= 11.2.0, < 11.2.9>= 11.3.0, < 11.3.6>= 11.4.0, < 11.4.4>= 11.5.0, < 11.5.4>= 11.6.0, < 11.6.1= 10.4.18= 11.2.9= 11.3.6= 11.4.4= 11.5.4= 11.6.1

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 10.4.18 / 11.2.9 / 11.3.6 or later
Fixed in 10.4.1811.2.911.3.6
Recommended fix High confidence

10.4.18, 11.2.9, 11.3.6, or 11.4.4 (latest stable in your major version line)

  1. 1. Identify your current Grafana version using the Grafana UI (Settings > About) or command line (`grafana-server -v`)
  2. 2. Determine which upgrade path applies based on your current version: if on 10.x, upgrade to 10.4.18; if on 11.2.x, upgrade to 11.2.9; if on 11.3.x, upgrade to 11.3.6; if on 11.4.x, upgrade to 11.4.4
  3. 3. Back up your Grafana database and configuration files before upgrading
  4. 4. Upgrade Grafana using your deployment method (package manager, Docker, or binary)
  5. 5. Verify the upgrade was successful by checking the Grafana version
  6. 6. Review Grafana logs to ensure normal startup
Caveat Minor version upgrades typically have low risk; review Grafana release notes for any breaking changes between your current version and target version

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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