dbcve.org
GrafanaApplication

CVE-2023-0507

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 8.5.21 / 9.2.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Grafana is an open-source platform for monitoring and observability. Starting with the 8.1 branch, Grafana had a stored XSS vulnerability affecting the core plugin GeoMap. The stored XSS vulnerability was possible due to map attributions weren't properly sanitized and allowed arbitrary JavaScript to be executed in the context of the currently authorized user of the Grafana instance. An attacker needs to have the Editor role in order to change a panel to include a map attribution containing JavaScript. This means that vertical privilege escalation is possible, where a user with Editor role can change to a known password for a user having Admin role if the user with Admin role executes malicious JavaScript viewing a dashboard. Users may upgrade to version 8.5.21, 9.2.13 and 9.3.8 to receive a fix.

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

Grafana versions 8.1+ contain a stored XSS vulnerability in the GeoMap plugin where map attributions are not properly sanitized, allowing execution of arbitrary JavaScript in the context of the authenticated user viewing the dashboard.

MitigationUpgrade Grafana to version 8.5.21, 9.2.13, or 9.3.8 or later. Until then, restrict Editor role permissions and disable or restrict the GeoMap panel plugin.

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.1.0, < 8.5.21>= 9.2.0, < 9.2.13>= 9.3.0, < 9.3.8

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed Grafana version
    Run `grafana-server -v` or check the version through the UI at Server Admin > Stats or via API: `curl -s http://localhost:3000/api/health`
    Affected if Version is 8.1.0 through 8.5.20, 9.2.0 through 9.2.12, or 9.3.0 through 9.3.7 (not fixed versions 8.5.21, 9.2.13, 9.3.8 or later)
  2. Verify GeoMap plugin is present
    Check plugin directory for geo folder or query the Grafana plugins API: `curl -s http://localhost:3000/api/plugins | grep -i geomap`
    Affected if GeoMap plugin is installed and enabled in the Grafana instance
  3. Identify dashboards using GeoMap panels
    Query the dashboards API: `curl -s http://localhost:3000/api/search?type=dash-db` then inspect each dashboard JSON for panels of type "geomap"
    Affected if Dashboards contain GeoMap panel configurations where malicious attribution strings could be stored
  4. Inspect GeoMap panel attribution configuration
    Open each dashboard with GeoMap panels, edit the panel, expand the Map section, and review the Attribution field for unsanitized HTML or JavaScript
    Affected if The Attribution field contains script tags, event handlers (onclick, onerror, etc.), or other potentially malicious HTML/JavaScript content that renders when viewing the dashboard

A user is affected if running a vulnerable Grafana version AND the GeoMap plugin is installed with dashboards containing GeoMap panels that have malicious script content in the Attribution field.

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 8.5.21 / 9.2.13 / 9.3.8 or later
Fixed in 8.5.219.2.139.3.8
Interim mitigation

Upgrade Grafana to version 8.5.21, 9.2.13, or 9.3.8 or later. Until then, restrict Editor role permissions and disable or restrict the GeoMap panel plugin.

Recommended fix High confidence

Upgrade to Grafana 8.5.21 (if on 8.x branch), 9.2.13 (if on 9.2.x branch), or 9.3.8 (if on 9.3.x branch)

  1. Identify your current Grafana version by checking the Grafana UI (Configuration > About) or running `grafana-server --version`
  2. Determine which upgrade path applies based on your current version: if on 8.x, upgrade to 8.5.21; if on 9.2.x, upgrade to 9.2.13; if on 9.3.x, upgrade to 9.3.8
  3. Back up your Grafana configuration (grafana.ini) and data directory before upgrading
  4. Upgrade Grafana using your package manager (e.g., `apt-get update && apt-get install grafana` for Debian/Ubuntu, or `yum update grafana` for RHEL/CentOS), or by downloading the appropriate package from grafana.com
  5. Restart the Grafana service after upgrade completes (e.g., `systemctl restart grafana-server`)
  6. Verify the new version is running and the GeoMap panel attribution field now properly sanitizes input
Caveat Minor/patch upgrades typically preserve configuration and data; however, review Grafana release notes for any deprecations or migration notes before upgrading

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

Fix this in Grafana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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