CVE-2025-6092VulnerabilityPublished 15 Jun 2025

CVE-2025-6092: comfyanonymous comfyui · Cross Site Scripting

Affects comfyanonymous comfyuiSource CVE Database V5

Mentioned vulnerabilities

CVE-2024-10099

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
PyPIcomfyui`pkg:pypi/comfyui`Other threats	Affected =0.3.0 =0.3.1 =0.3.2 =0.3.3 =0.3.4 =0.3.5 =0.3.6 =0.3.7 =0.3.8 =0.3.9 =0.3.10 =0.3.11 =0.3.12 =0.3.13 =0.3.14 =0.3.15 =0.3.16 =0.3.17 =0.3.18 =0.3.19 =0.3.20 =0.3.21 =0.3.22 =0.3.23 =0.3.24 =0.3.25 =0.3.26 =0.3.27 =0.3.28 =0.3.29 =0.3.30 =0.3.31 =0.3.32 =0.3.33 =0.3.34 =0.3.35 =0.3.36 =0.3.37 =0.3.38 =0.3.39	Fixed in–

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

AI-suggested

1. Implement Web Application Firewall (WAF) rules specifically targeting the /upload/image endpoint to detect and block suspicious payloads containing script tags or common XSS vectors. 2. Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and limit the domains from which scripts can be loaded, mitigating the impact of successful XSS attacks. 3. Sanitize and validate all user inputs on the server side, especially the 'image' parameter, using robust libraries or frameworks that enforce strict input validation and output encoding. 4. Isolate the vulnerable ComfyUI instance behind authentication and restrict access to trusted users only, reducing exposure to unauthenticated attackers. 5. Monitor application logs and network traffic for unusual activity related to the /upload/image endpoint to detect potential exploitation attempts early. 6. If feasible, disable or restrict the image upload functionality temporarily until a vendor patch or official fix is available. 7. Educate users about the risks of clicking on suspicious links or interacting with untrusted content within the ComfyUI environment. 8. Conduct regular security assessments and penetration testing focused on web application vulnerabilities, including XSS, to identify and remediate similar issues proactively. 9. Engage with the vendor or community to encourage timely patch development and share threat intelligence related to this vulnerability.

Description

A vulnerability was found in comfyanonymous comfyui up to 0.3.39. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /upload/image of the component Incomplete Fix CVE-2024-10099. The manipulation of the argument image leads to cross site scripting. The attack can be launched 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.

Impact

For European organizations using ComfyUI, this vulnerability poses a significant risk to web application security and user trust. Exploitation could lead to session hijacking, unauthorized actions performed on behalf of users, theft of sensitive information accessible via the browser, and potential spread of malware through malicious scripts. Organizations in sectors such as finance, healthcare, and government, where data integrity and confidentiality are paramount, could face reputational damage and regulatory penalties if user data is compromised. The vulnerability's remote and unauthenticated nature increases the attack surface, especially for public-facing deployments. Additionally, the lack of vendor response and patch availability prolongs exposure, making timely mitigation critical. The incomplete fix history suggests potential for further related vulnerabilities, emphasizing the need for comprehensive security reviews. The medium severity rating indicates that while the vulnerability is not critical, it can be leveraged as part of a broader attack chain or social engineering campaign, amplifying its impact. European organizations relying on ComfyUI for internal or external web services should be aware of the risk of client-side attacks that could undermine user confidence and lead to compliance issues under regulations like GDPR.

Summary

CVE-2025-6092 is a cross-site scripting (XSS) vulnerability affecting the ComfyUI product developed by comfyanonymous, specifically in versions up to 0.3.39. The vulnerability resides in the /upload/image endpoint, where improper handling of the 'image' parameter allows an attacker to inject malicious scripts. This vulnerability is a result of an incomplete fix for a previous vulnerability (CVE-2024-10099), indicating that the underlying issue was not fully remediated. The attack vector is remote and does not require authentication, making it accessible to any unauthenticated attacker who can send crafted requests to the vulnerable endpoint. The vulnerability requires user interaction (UI:P) in the sense that the victim must load or interact with the maliciously crafted content for the XSS payload to execute. The CVSS 4.0 score is 5.3 (medium severity), reflecting a moderate impact primarily on the integrity of the affected system, with limited impact on confidentiality and availability. The exploit has been publicly disclosed, increasing the risk of exploitation, although no known exploits in the wild have been reported at this time. The vulnerability allows attackers to execute arbitrary JavaScript in the context of the victim's browser session, potentially leading to session hijacking, defacement, or redirection to malicious sites. Given the nature of the vulnerability, it primarily threatens web applications and users interacting with the ComfyUI interface, especially those uploading or viewing images via the vulnerable endpoint.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jun 2025, 17:49 UTC

Technical details

References

Community reviews

Related threats