Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain API or MCP token
-
DeliveryStore template with HTML event handler
-
ExploitVictim opens template preview
-
ExecutionUnsanitized HTML executes script
-
ImpactAbuse window.edgeeverDesktop privileged bridge
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid EdgeEver API or MCP token with permission to write/store templates (authenticated, PR:L) and requires a user to open the affected template preview (UI:P), at which point TemplatesPane.tsx renders template contentMarkdown through dangerouslySetInnerHTML without sanitization, allowing HTML event-handler payloads to execute and reach the privileged window.edgeeverDesktop bridge. It affects EdgeEver desktop versions 1.6.0 through 1.112.0. Limiting factors that reduce realistic risk: the attacker must first obtain a template-writing token, and a victim must actively open the preview - there is no fully unauthenticated, zero-interaction path. |
| Impact | The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H) scores 8.5, reflecting a network-reachable, low-complexity stored XSS with high confidentiality and integrity impact but requiring low-level privileges (a valid API or MCP token) and passive user interaction (opening a preview). No EPSS score, CISA KEV listing, or public proof-of-concept was provided, so there is no public exploit identified at time of analysis - the high score is driven by potential impact (script execution reaching the privileged window.edgeeverDesktop bridge in what appears to be an Electron desktop app), not by evidence of active exploitation. The two gating conditions (PR:L authenticated token write + UI:P victim preview) meaningfully reduce real-world risk versus a fully unauthenticated, no-interaction flaw, and the affected product is an obscure open-source project with a negligible deployment footprint. Net: a legitimately high-impact bug worth patching for EdgeEver users, but not a broad-ecosystem emergency - prioritize based on whether you run EdgeEver and issue tokens to untrusted parties, not on the 8.5 alone. |
| Exploit ScenarioDerived | An attacker holding a valid EdgeEver API or MCP token creates a template whose contentMarkdown embeds HTML with event handlers (e.g. an onerror/onload payload). When a user opens the template preview, TemplatesPane.tsx renders the raw HTML via dangerouslySetInnerHTML without sanitization, executing attacker script in the privileged desktop renderer and exposing the window.edgeeverDesktop bridge. No public exploit code was identified; the network attack vector is low-complexity but gated by token access and the victim opening the preview. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Stored cross-site scripting in EdgeEver 1.6.0 through 1.112.0 allows an attacker with a valid API or MCP token to inject HTML event handlers into template contentMarkdown, which executes when a victim opens the template preview, granting access to the privileged window.edgeeverDesktop bridge. Exploitation requires a low-privileged authenticated token (PR:L) and user interaction to open the preview (UI:P), and no public exploit code has been identified at time of analysis.
RemediationAI
Upstream fix available (commit 6b5027e8b4becbee0c0de7cd1a3d04af78ca87ca); released patched version not independently confirmed. Verify that the fix sanitizes template contentMarkdown before rendering (e.g., using DOMPurify or equivalent) and removes the use of dangerouslySetInnerHTML. Until a patched version is confirmed, restrict template write access to trusted users, avoid previewing untrusted templates, and consider enforcing a strict Content Security Policy in the Electron renderer to mitigate XSS. Monitor the vendor repository and issues 533 and 546 for updates. Advisory: https://www.vulncheck.com/advisories/edgeever-1.6.0-through-1.112.0-stored-xss-via-templatespane-template-preview.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in apps/web/src/components/TemplatesPane.tsx (lines 150-158), where template contentMarkdown is rendered with dangerouslySetInnerHTML without sanitization. This is a classic CWE-79 stored XSS: an attacker with write access to templates (via API or MCP token) can persist malicious HTML containing event handlers (e.g., onerror) that execute in the context of the EdgeEver desktop renderer when the template is previewed. Because the XSS runs in the Electron renderer, it can access the privileged window.edgeeverDesktop bridge, potentially enabling further abuse of desktop APIs. The referenced fix commit (6b5027e8b4becbee0c0de7cd1a3d04af78ca87ca) modifies ACP host and path validation code, not the vulnerable TemplatesPane component, so the exact patch for this XSS is not evident from the provided diff; however, the commit is listed among the references.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Token-authenticated write gives PR:L and victim preview gives UI:R; stored script escaping the web content into the privileged desktop bridge justifies S:C with high C and I, no availability impact.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
EdgeEver 1.6.0 through 1.112.0 contains a stored cross-site scripting vulnerability in TemplatesPane.tsx that renders template contentMarkdown with raw HTML via dangerouslySetInnerHTML without sanitization. Attackers can write templates containing HTML event handlers through an API or MCP token to run script on preview and access the privileged window.edgeeverDesktop bridge.
Executive ViewAI
A stored cross-site scripting vulnerability affects EdgeEver versions 1.6.0 through 1.112.0, allowing anyone holding a low-privileged API or MCP token to embed malicious content in template previews that then executes inside the privileged window.edgeeverDesktop bridge of any colleague who opens the template. Because that bridge reaches desktop-level capabilities, a single compromised or over-scoped integration token could translate into attacker control of end-user workstations and any data those users can access. No vendor-released patch is identified and no public exploit code has been identified at time of analysis, but the flaw is rated HIGH (CVSS 8.5) and requires only authenticated low-privilege access plus a routine user action.
No vendor-released patch identified at time of analysis. Interim mitigations: revoke or rotate all API/MCP tokens and enforce least privilege on remaining ones; disable or restrict the template preview feature; isolate or disable the window.edgeeverDesktop bridge where feasible; isolate template authoring from consumption and require review of contentMarkdown changes; apply a restrictive Content Security Policy and sanitize rendered markdown; monitor and alert on template modifications, preview opens, and bridge activity; segment EdgeEver hosts to limit blast radius; accelerate migration to an alternative platform if isolation cannot be achieved.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-97881
GHSA-f2xf-xr5r-qf3x
NVD
CVE.org
EPSS
Exploit-DB