Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to ComfyUI
-
DeliverySubmit XSS payload via userdata endpoint
-
ExploitPayload stored in user data
-
ExecutionVictim views attacker's profile
-
PersistMalicious script executes in victim's browser
-
ImpactAttacker harvests session token or credentials
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: (1) Valid authentication to the ComfyUI instance (PR:L); (2) Ability to submit data to the getuserdata endpoint or user profile modification endpoint (no special configuration needed for standard deployments); (3) Another user must view the attacker's injected data or click a link containing the malicious payload (UI:R). The vulnerability is NOT exploitable against default configurations without a login credential. Exploitation is limited to the user's current security context (S:U) - XSS payload cannot escalate privileges or access other users' data directly but can steal session cookies or perform actions as the victim. |
| Impact | CVSS 3.5 (Low) with EPSS data unavailable suggests limited real-world risk despite public exploit availability. The Low CVSS reflects mandatory constraints: PR:L (login required), UI:R (user interaction required), and S:U (scope unchanged-impact limited to same security context). CVSS vector shows AC:L (low complexity) and AV:N (network-accessible), making exploitation straightforward once authenticated, but the authentication and interaction barriers significantly reduce attack surface. Public exploit availability (POC confirmed) increases concern for targeted attacks against ComfyUI instances, but absence from CISA KEV indicates no confirmed active exploitation in the wild at analysis time. Risk is elevated in multi-user ComfyUI deployments where an attacker with login access could inject payloads affecting other users, particularly if the instance is exposed to untrusted networks. For single-user local installations, risk is minimal. E:P (exploit code mature/proof-of-concept exists) and RL:X (vendor has not issued a patch) compound the remediation burden. |
| Exploit ScenarioDerived | An authenticated attacker logs into a ComfyUI instance and injects malicious JavaScript into a user profile field (e.g., username, email, or preferences) via the userdata endpoint. When another user or an administrator views the attacker's profile or user list, the injected script executes in their browser with their session privileges, allowing session hijacking, credential theft, or further system compromise. The publicly available exploit (gist.github.com/YLChen-007/50f0cdc5e3f7b737ce99c783e487ca0d) provides proof-of-concept payloads. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 20, 2026
Stored cross-site scripting (XSS) in ComfyUI's userdata endpoint (getuserdata function in app/user_manager.py) allows authenticated attackers to inject malicious scripts that execute in other users' browsers. Affected versions range from 0.1 through 0.13.0. The vulnerability requires user interaction (UI:R) and authenticated access (PR:L), limiting real-world impact, but publicly available exploit code exists and the vendor has not responded to disclosure.
RemediationAI
No vendor-released patch identified at time of analysis - the vendor was contacted early but did not respond. Immediate remediation options include: (1) Upgrade to a patched version if available (verify with upstream project or official release channels for versions after 0.13.0); (2) Apply input validation and output encoding to the getuserdata function in app/user_manager.py - specifically, HTML-encode or sanitize all user-controlled data before inclusion in responses; (3) Implement Content Security Policy (CSP) headers with script-src 'self' to restrict inline script execution; (4) Restrict userdata endpoint access via network segmentation or authentication gateway if ComfyUI is exposed to untrusted networks; (5) For high-risk deployments, disable the userdata endpoint or user profile features if operationally feasible. Monitor upstream ComfyUI repository and issue trackers for security patches. Refer to VulDB (vuldb.com/vuln/358227) for updates.
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
ComfyUI is a node-based UI for Stable Diffusion that manages user data via a REST endpoint. The userdata endpoint's getuserdata function fails to sanitize user-supplied input before reflecting it in HTTP responses, creating a stored XSS vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation). The attack surface is the app/user_manager.py component, specifically the endpoint handling user profile or preference data. Because the CVSS vector specifies PR:L (requires login) and UI:R (requires user interaction to trigger the payload), exploitation is limited to authenticated users and requires a victim to view the malicious data in their own session or click a crafted link.
Know when Comfyui gets its next vulnerability
- 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:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
6DescriptionCVE.org
A vulnerability has been found in ComfyUI up to 0.13.0. Affected by this vulnerability is the function getuserdata of the file app/user_manager.py of the component userdata Endpoint. Such manipulation leads to cross site scripting. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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.
Related Vulnerabilities in ComfyUI Multiple Vulnerabilities
View all 5Arbitrary file write via path traversal in ComfyUI before 0.30.0 lets an attacker place attacker-controlled content anyw
comfyanonymous/comfyui version v0.2.4 suffers from a non-blind Server-Side Request Forgery (SSRF) vulnerability. Rated h
A stored cross-site scripting (XSS) vulnerability exists in comfyanonymous/comfyui version 0.2.2 and possibly earlier. R
Remote code execution in ComfyUI v0.23.0 (and all prior 0.x releases) lets unauthenticated attackers run arbitrary Pytho
Stored cross-site scripting in ComfyUI (Comfy-Org) before 0.28.0 lets an attacker upload HTML or SVG to the per-user use
Stored cross-site scripting in ComfyUI before 0.28.0 lets an attacker upload a malicious SVG that the /view endpoint ser
Unauthenticated information disclosure in ComfyUI (comfy-org/comfyui) before 0.28.0 lets remote attackers read arbitrary
Path traversal arbitrary file read in ComfyUI (comfy-org) before 0.28.0 lets remote unauthenticated attackers probe arbi
EUVD-2026-23737
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB