Worldmap PanelApplication · Grafana

CVE-2023-3010

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-25

Fix available

A fix is available. Upgrade to 1.0.4 or later.

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Grafana is an open-source platform for monitoring and observability. The WorldMap panel plugin, versions before 1.0.4 contains a DOM XSS vulnerability.

Technical summary

dbcve analysis · high confidence

The WorldMap panel plugin for Grafana versions before 1.0.4 contains a DOM-based Cross-Site Scripting (XSS) vulnerability. This client-side vulnerability allows attackers to inject malicious scripts through the plugin's handling of map data rendered in the browser without proper sanitization.

MitigationUpdate the WorldMap panel plugin to version 1.0.4 or later to apply the security patch that addresses the DOM XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Worldmap PanelApplication

Affected:< 1.0.4

CVSS breakdown

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

Am I affected?

dbcve checks

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

Identify if WorldMap panel plugin is installed

Check the Grafana plugins directory for the worldmap-panel plugin folder. In typical Grafana installations, this is located at /var/lib/grafana/plugins/ or queried via the Grafana API at /api/plugins search for 'worldmap'.

Affected if The worldmap-panel plugin folder exists in the plugins directory.
Determine the installed version of the WorldMap panel plugin

Locate the plugin.json file within the worldmap-panel plugin directory and read the 'version' field. Alternatively, use the Grafana CLI command 'grafana-cli plugins ls' to list installed plugins and their versions.

Affected if The version field shows a version number lower than 1.0.4.
Verify plugin is enabled in Grafana

Check Grafana configuration file (grafana.ini) for the 'app_mode' setting and confirm the plugin is not explicitly disabled. Query the Grafana API endpoint /api/plugins to confirm the plugin status is 'installed' and 'enabled'.

Affected if The plugin appears in the enabled plugins list in Grafana configuration.
Check if panel instances using WorldMap exist

Review existing Grafana dashboards by querying the database or inspecting dashboard JSON files for panels with 'type': 'worldmap' or 'type': 'grafana-worldmap-panel'. Use Grafana API: GET /api/search?type=dash-db to find dashboards, then GET /api/dashboards/uid/{uid} to inspect panel types.

Affected if Any dashboard contains a panel configured with the worldmap plugin type.

A user is affected if the WorldMap panel plugin is installed, enabled in Grafana, and the installed version is lower than 1.0.4.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.0.4 or later

Fixed in 1.0.4

Interim mitigation

Update the WorldMap panel plugin to version 1.0.4 or later to apply the security patch that addresses the DOM XSS vulnerability.

Recommended fix High confidence

WorldMap Panel version 1.0.4

Open Grafana and navigate to Administration > Plugins and data > Plugins (or similar path depending on Grafana version)
Search for 'WorldMap' or 'Worldmap Panel' in the plugins list
Click on the WorldMap panel plugin
If an update is available, click the 'Update' or 'Upgrade' button
Confirm the upgrade to version 1.0.4
Restart Grafana services if required to load the updated plugin
Clear browser cache and verify the plugin version shows 1.0.4

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

Fix this in Worldmap Panel Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing1.0 h
Review / QA1.0 h

4.0 hours of engineering $750

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

grafana.comVendor Advisory
security.netapp.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3010 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-3010?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 1.0.4 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Worldmap Panel

Remediation

Need this fixed?

Fix this in Worldmap Panel 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2023-3010 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References