Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Remote script delivery with low complexity but requiring operator interaction (UI:R); Electron renderer breakout justifies S:C with high C/I/A in the client context.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
7DescriptionNVD
Improper neutralization of input during web page generation ('cross-site scripting') in Azure Storage Explorer allows an unauthorized attacker to elevate privileges over a network.
AnalysisAI
Privilege elevation via stored/reflected cross-site scripting in Microsoft Azure Storage Explorer (versions prior to 20260730.9) lets a remote attacker inject script that executes in a victim's session when they view attacker-influenced content, enabling scope-changing takeover of the application context. Rated CVSS 9.6 because the scope change (S:C) lets injected code cross the security boundary of the Electron-based client, though exploitation requires the victim to interact with the malicious content (UI:R). No public exploit has been identified at time of analysis; EPSS is a modest 0.81% (54th percentile).
Technical ContextAI
Azure Storage Explorer is Microsoft's cross-platform desktop client (built on Electron/Chromium) for managing Azure Storage accounts, blobs, files, queues, tables, and Azure Data Lake. The flaw is CWE-79, improper neutralization of input during web page generation, meaning attacker-controlled data - plausibly metadata such as blob/container names, tags, or other storage-object properties rendered by the client's web UI - is emitted into the page without adequate encoding. In an Electron application, script that executes inside the renderer can reach beyond a pure browser sandbox, which aligns with the CVSS scope change (S:C) and the privilege-elevation framing. The single affected product per CPE is cpe:2.3:a:microsoft:azure_storage_explorer.
RemediationAI
Vendor-released patch: upgrade Azure Storage Explorer to version 20260730.9 or later, per the Microsoft MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-57104; this is the primary and recommended fix. Until the update is deployed, reduce exposure by avoiding the rendering of storage objects (containers, blobs, file shares, tags, and metadata) originating from untrusted or shared storage accounts, and restrict use of the tool to storage accounts your team controls - the trade-off is reduced operational convenience when triaging third-party or customer-supplied data. Because exploitation requires the operator to view attacker-influenced content, limiting who uses the client against untrusted accounts and enforcing least-privilege on the Azure credentials the client authenticates with limits blast radius if injection occurs. No independent, code-level workaround is documented, so treat upgrading as the durable control.
More in Azure Storage Explorer
View allSame weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-56590
GHSA-cxf2-4x8x-vqf5