CVE-2025-4123

CRITICALNVD 7.69.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 97% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-16107 (ENISA EUVD) · GHSA-q53q-gxq9-mgrj (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 97%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 97%CVSS: 7.6Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.6
EG Score
9.0CRITICALhigh confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation97% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
97%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.6 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
97% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 22, 2025

Last Modified

April 29, 2026

Advisory Details (3)

Auto-updated Apr 29, 2026
Patch available.
Web page

Grafana 11.6.0 - SSRF - Multiple webapps Exploit

https://www.exploit-db.com/exploits/52491
Web page

XSS in Frontend Plugins in Grafana | Grafana Labs

https://grafana.com/security/security-advisories/cve-2025-4123/
Web page

Grafana security release: Medium and high severity security fixes for CVE-2025-4123 and CVE-2025-3580 | Grafana Labs

https://grafana.com/blog/2025/05/23/grafana-security-release-medium-and-high-severity-security-fixes-for-cve-2025-4123-and-cve-2025-3580/

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrafana-0:9.2.10-23.el9_42025-06-09redhat
redhatgrafana-0:7.3.6-9.el8_42025-06-09redhat
redhatgrafana-0:7.5.15-7.el8_82025-06-09redhat
redhatgrafana-0:7.5.11-10.el9_02025-06-09redhat
redhatgrafana-0:6.3.6-7.el8_22025-06-09redhat
redhatgrafana-0:7.5.11-6.el8_62025-06-09redhat
redhatgrafana-0:9.0.9-8.el9_22025-06-09redhat
redhatgrafana-0:10.2.6-17.el10_02025-05-19redhat
redhatgrafana-0:9.2.10-23.el8_102025-05-19redhat
redhatgrafana-0:10.2.6-13.el9_62025-05-19redhat
gogithub.com/grafana/grafana @ 0.0.0-20250521183405-c7a690348df7 (fixes < 0.0.0-20250521183405-c7a690348df7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/grafana/grafana—
  • every version up to 0.0.0-20250521183405-c7a690348df7: fixed in 0.0.0-20250521183405-c7a690348df7
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 155 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 62 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 12:40 UTCEG score recompute
  2. 2026-11-02 12:40 UTCVendor advisory
  3. 2026-11-02 12:40 UTCGHSA enrichmentGHSA-q53q-gxq9-mgrj · GitHub severity HIGH · GitHub CVSS 7.6
  4. 2026-11-01 13:10 UTCVendor advisory
  5. 2026-11-01 13:10 UTCGHSA enrichmentGHSA-q53q-gxq9-mgrj · GitHub severity HIGH · GitHub CVSS 7.6
  6. 2026-11-01 08:06 UTCGHSA enrichmentGHSA-q53q-gxq9-mgrj · GitHub severity HIGH · GitHub CVSS 7.6
  7. 2026-11-01 08:06 UTCEG score recompute
  8. 2026-10-31 13:39 UTCEG score recompute
  9. 2026-10-31 13:39 UTCVendor advisory
  10. 2026-10-30 14:09 UTCEG score recompute
  11. 2026-10-30 14:09 UTCVendor advisory
  12. 2026-10-29 14:38 UTCEG score recompute
  13. 2026-10-29 14:38 UTCVendor advisory
  14. 2026-10-28 15:09 UTCEG score recompute
  15. 2026-10-28 15:09 UTCVendor advisory
  16. 2026-10-27 15:39 UTCEG score recompute
  17. 2026-10-27 15:39 UTCVendor advisory
  18. 2026-10-26 16:07 UTCVendor advisory
  19. 2026-10-25 16:31 UTCEG score recompute
  20. 2026-10-25 16:31 UTCVendor advisory
  21. 2026-10-25 16:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  22. 2026-10-25 16:27 UTCEG score recompute
  23. 2026-10-24 16:59 UTCEG score recompute
  24. 2026-10-24 16:59 UTCVendor advisory
  25. 2026-10-23 17:30 UTCEG score recompute
Show 68 more
  1. 2026-10-23 17:30 UTCVendor advisory
  2. 2026-10-22 18:00 UTCEG score recompute
  3. 2026-10-22 18:00 UTCVendor advisory
  4. 2026-10-21 18:05 UTCEG score recompute
  5. 2026-10-21 18:05 UTCVendor advisory
  6. 2026-10-20 18:35 UTCEG score recompute
  7. 2026-10-20 18:35 UTCVendor advisory
  8. 2026-10-20 16:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  9. 2026-10-19 19:04 UTCEG score recompute
  10. 2026-10-19 19:04 UTCVendor advisory
  11. 2026-10-19 16:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  12. 2026-10-18 19:27 UTCEG score recompute
  13. 2026-10-18 19:27 UTCVendor advisory
  14. 2026-10-18 16:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  15. 2026-10-18 05:34 UTCEG score recompute
  16. 2026-10-17 19:56 UTCEG score recompute
  17. 2026-10-17 19:56 UTCVendor advisory
  18. 2026-10-16 20:25 UTCEG score recompute
  19. 2026-10-16 20:25 UTCVendor advisory
  20. 2026-10-15 17:51 UTCEG score recompute
  21. 2026-10-15 17:51 UTCVendor advisory
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  23. 2026-10-14 16:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  24. 2026-10-14 11:44 UTCEG score recompute
  25. 2026-10-14 11:44 UTCVendor advisory
  26. 2026-10-13 10:48 UTCVendor advisory
  27. 2026-10-12 17:05 UTCEG score recompute
  28. 2026-10-12 11:18 UTCVendor advisory
  29. 2026-10-11 20:38 UTCEG score recompute
  30. 2026-10-11 18:49 UTCEG score recompute
  31. 2026-10-11 15:26 UTCEG score recompute
  32. 2026-10-07 23:47 UTCEPSS rescoreEPSS 97% · 99th percentile
  33. 2026-09-30 19:14 UTCOSV refresh
  34. 2026-09-24 14:02 UTCEPSS rescoreEPSS 97% · 99th percentile
  35. 2026-09-21 21:06 UTCEPSS rescoreEPSS 97% · 99th percentile
  36. 2026-09-12 01:53 UTCOSV refresh
  37. 2026-09-10 09:34 UTCEPSS rescoreEPSS 97% · 99th percentile
  38. 2026-09-06 13:46 UTCEPSS rescoreEPSS 97% · 99th percentile
  39. 2026-09-05 15:28 UTCEPSS rescoreEPSS 97% · 99th percentile
  40. 2026-08-30 19:16 UTCEPSS rescoreEPSS 97% · 99th percentile
  41. 2026-08-28 21:40 UTCEPSS rescoreEPSS 97% · 99th percentile
  42. 2026-08-24 14:16 UTCEPSS rescoreEPSS 97% · 99th percentile
  43. 2026-08-24 09:22 UTCEPSS rescoreEPSS 97% · 99th percentile
  44. 2026-08-24 07:28 UTCOSV refresh
  45. 2026-08-23 00:18 UTCEPSS rescoreEPSS 98% · 99th percentile
  46. 2026-08-12 13:50 UTCEPSS rescoreEPSS 98% · 99th percentile
  47. 2026-08-11 13:41 UTCEPSS rescoreEPSS 98% · 99th percentile
  48. 2026-08-08 04:19 UTCOSV refresh
  49. 2026-08-04 10:37 UTCEPSS rescoreEPSS 98% · 99th percentile
  50. 2026-08-03 10:35 UTCEPSS rescoreEPSS 98% · 99th percentile
  51. 2026-07-24 14:17 UTCEPSS rescoreEPSS 98% · 99th percentile
  52. 2026-07-23 02:55 UTCEG score recompute
  53. 2026-07-22 21:21 UTCEG score recompute▲ 1.40
  54. 2026-07-22 21:21 UTCVendor advisory
  55. 2026-07-22 14:07 UTCEPSS rescoreEPSS 98% · 99th percentile
  56. 2026-07-21 15:24 UTCEPSS rescoreEPSS 98% · 99th percentile
  57. 2026-07-15 16:57 UTCEPSS rescoreEPSS 98% · 99th percentile
  58. 2026-07-12 05:46 UTCEPSS rescoreEPSS 98% · 99th percentile
  59. 2026-07-10 12:11 UTCOSV refresh
  60. 2026-06-30 23:22 UTCEPSS rescoreEPSS 98% · 99th percentile
  61. 2026-06-28 14:07 UTCEPSS rescoreEPSS 94% · 99th percentile
  62. 2026-06-27 03:08 UTCEPSS rescoreEPSS 95% · 99th percentile
  63. 2026-06-23 21:32 UTCEPSS rescoreEPSS 95% · 99th percentile
  64. 2026-06-21 21:43 UTCOSV refresh
  65. 2026-06-16 17:52 UTCEPSS rescoreEPSS 95% · 99th percentile
  66. 2026-06-15 17:48 UTCEPSS rescoreEPSS 95% · 99th percentile
  67. 2026-06-14 23:17 UTCEPSS rescoreEPSS 6.9% · 91st percentile
  68. 2026-06-13 23:00 UTCEPSS rescoreEPSS 6.9% · 91st percentile

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 3 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-52491
    Published Apr 6, 2026

    Grafana 11.6.0 - SSRF

    Open source ↗
  • GitHub PoCpunitdarji/Grafana-cve-2025-4123
    Published Jun 21, 2025
    Open source ↗
  • GitHub PoCynsmroztas/CVE-2025-4123-Exploit-Tool-Grafana-
    Published Jun 4, 2025

    CVE-2025-4123 - Grafana Tool

    Open source ↗
  • GitHub PoCNightBloodZ/CVE-2025-4123
    Published May 22, 2025

    Script to exploit Grafana CVE-2025-4123: XSS and Full-Read SSRF

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-4123.yaml
    Published May 22, 2025

    Grafana - XSS / Open Redirect / SSRF via Client Path Traversal

    Open source ↗

Frequently asked(5)

What is CVE-2025-4123?
CVE-2025-4123 is a critical-severity vulnerability; its CVE record was published on May 22, 2025. 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…
When was the CVE record for CVE-2025-4123 published?
The CVE record for CVE-2025-4123 was published on May 22, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2025-4123 actively exploited?
CVE-2025-4123 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-4123?
CVE-2025-4123 has a CVSS v3 base score of 7.6 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2025-4123?
A fix for CVE-2025-4123 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-4123 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-4123

Explore →

Is Your Infrastructure Affected by CVE-2025-4123?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.