Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2023-1410

MEDIUM

CVE-2023-1410 is a medium-severity (CVSS 6.2) Cross-site Scripting (XSS) vulnerability in github.com/grafana/grafana. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2023-1410 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Stored XSS in Graphite FunctionDescription tooltip

Also known asBIT-grafana-2023-1410GHSA-qrrg-gw7w-vp76
Published
Mar 23, 2023
Updated
Jul 15, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

Blast Radius

4 pkgs affected
🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Grafana is an open-source platform for monitoring and observability. 

Grafana had a stored XSS vulnerability in the Graphite FunctionDescription tooltip.

The stored XSS vulnerability was possible due the value of the Function Description was not properly sanitized.

An attacker needs to have control over the Graphite data source in order to manipulate a function description and a Grafana admin needs to configure the data source, later a Grafana user needs to select a tampered function and hover over the description. 

Users may upgrade to version 8.5.22, 9.2.15 and 9.3.11 to receive a fix.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafana8.0.0&&< 8.5.228.5.22
🐹Gogithub.com/grafana/grafana9.3.0&&< 9.3.119.3.11
🐹Gogithub.com/grafana/grafana9.4.0&&< 9.4.79.4.7
🐹Gogithub.com/grafana/grafana9.0.0&&< 9.2.159.2.15
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/grafana/grafana to 8.5.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-1410 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-1410 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-1410. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Grafana is an open-source platform for monitoring and observability.  Grafana had a stored XSS vulnerability in the Graphite FunctionDescription tooltip. The stored XSS vulnerability was possible due the value of the Function Description was not properly sanitized. An attacker needs to have control over the Graphite data source in order to manipulate a function description and a Grafana admin needs to configure the data source, later a Grafana user needs to select a tampered function and hover over the description.  Users may upgrade to version 8.5.22, 9.2.15 and 9.3.11 to receive a fix
O3 Security · Impact-Aware SCA

Is CVE-2023-1410 in your dependencies?

O3 detects CVE-2023-1410 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.