VulnerabilityPublished 11 Mar 2026

CVE-2026-32117: ekacnet grafanacubism-panel · Cross-site Scripting

Affects ekacnet grafanacubism-panelSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.6 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ekacnetgrafanacubism-panel	Affected <=0.1.2	Fixed in–
GitHubekacnet/grafanacubism-panel`pkg:github/ekacnet/grafanacubism-panel`Other threats	Affected <=0.1.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-32117, organizations should first upgrade the grafanacubism-panel plugin to a version later than 0.1.2 once a patch is released. Until then, restrict dashboard editor privileges strictly to trusted and verified users to minimize the risk of malicious URL injection. Implement input validation and sanitization on URLs supplied to the zoom-link handler, ensuring that only safe schemes such as http and https are allowed, and explicitly block javascript: or other dangerous schemes. Consider disabling or restricting the use of the cubism-panel plugin if it is not essential. Employ Content Security Policy (CSP) headers to restrict execution of inline scripts and untrusted JavaScript. Monitor Grafana logs for unusual dashboard edits or suspicious drag-zoom actions. Educate users about the risk of interacting with untrusted dashboards. Finally, maintain up-to-date Grafana and plugin versions and subscribe to vendor security advisories for timely patching.

Description

CVE-2026-32117 is a high-severity cross-site scripting (XSS) vulnerability in the ekacnet grafanacubism-panel plugin for Grafana versions 0.1.2 and earlier. The flaw arises because the panel’s zoom-link handler directly passes a dashboard editor-supplied URL to window.location.assign() or window.open() without validating the URL scheme. An attacker with dashboard editor privileges can inject a javascript: URI, which executes malicious code in the context of the Grafana origin when any viewer performs a drag-zoom action on the panel. This vulnerability requires at least editor-level privileges and user interaction but can lead to high confidentiality impact by stealing session tokens or performing actions on behalf of the user. No known exploits are currently reported in the wild.

Impact

The primary impact of this vulnerability is the potential compromise of confidentiality within Grafana instances using the vulnerable plugin. An attacker with editor privileges can execute arbitrary JavaScript in the context of the Grafana web application, potentially stealing session cookies, tokens, or other sensitive data accessible to the browser. This can lead to account takeover or unauthorized access to dashboards and data visualizations. The integrity impact is limited but could allow manipulation of the user interface or injection of misleading information. Availability is not affected. Since exploitation requires editor privileges, the risk is mitigated by restricting such privileges to trusted users. However, in environments where editor roles are widely granted or compromised, this vulnerability could facilitate lateral movement or privilege escalation. Organizations relying on Grafana for monitoring critical infrastructure or business data could face significant operational and reputational risks if attackers leverage this vulnerability to gain unauthorized access or disrupt monitoring workflows.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:22 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats