Skip to main content

Clarity Upscaler EUVDEUVD-2026-98181

| CVE-2026-108942 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-13 VulDB GHSA-66qr-3w6p-3g37
5.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to WebUI with low privileges
  2. Delivery
    Inject script into network card Description
  3. Exploit
    Victim opens Extra Networks tab
  4. Execution
    Payload executes in victim browser
  5. Impact
    Perform actions in victim's session

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 low-privileged authenticated actor (PR:L) who can set or influence the 'Description' metadata of an Extra Networks card - for example by introducing a crafted model/network file whose card metadata is rendered by create_html_for_item - and a second victim user must subsequently view that card in the Extra Networks UI (passive user interaction, UI:P). Limiting factors: the flaw is only meaningfully reachable on deployments that serve multiple users or load untrusted/third-party model files; a default single-user local WebUI where the operator controls all model metadata has little realistic exposure. Impact is confined to the victim's browser context (low integrity impact, no confidentiality or availability impact per the vector).

Impact

This is a medium-severity, low-priority issue in practice. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N, score 5.1) describes a network-reachable but authenticated (PR:L) stored cross-site scripting flaw that additionally requires passive victim interaction (UI:P) and yields only low integrity impact with no confidentiality or availability impact. No EPSS score was supplied in the input, so exploitation probability cannot be quantified. The CVE is not listed in CISA KEV and no public exploit code is referenced - only a VulDB entry and an unanswered upstream issue report exist. There is no conflict between the signals: all of them point to a constrained, operator/multi-user-dependent XSS rather than a mass-exploitable RCE. The combination of required low-level authentication plus required user interaction means this is a real-priority finding only for deployments that expose the WebUI to multiple or untrusted users; for the common single-user local deployment the practical risk is minimal. Note that EPSS data is entirely absent and should be checked separately before final prioritization.

Exploit ScenarioDerived

On a multi-user or internet-exposed Clarity Upscaler / stable-diffusion-webui instance, a low-privileged user supplies a model or network-card whose Description metadata contains a malicious script payload. When another user (e.g., an administrator) opens the Extra Networks tab and the card is rendered by create_html_for_item, the unescaped Description executes JavaScript in the victim's browser session. No public exploit code is identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Stored cross-site scripting in philz1337x/clarity-upscaler allows a low-privileged authenticated user to execute script in another user's browser by manipulating the Description metadata of an Extra Networks card, which is then rendered unescaped by create_html_for_item in modules/ui_extra_networks.py. Every repository version is affected because the project ships as a rolling release whose codebase descends from AUTOMATIC1111/stable-diffusion-webui v1.7.0; the upstream project fixed the same flaw in v1.8.0 (March 1, 2024), but clarity-upscaler's maintainers were notified early via an issue report and have not responded. No public exploit has been identified at time of analysis, and practical exposure is limited to multi-user instances or deployments that load untrusted third-party model files, since a single-user local WebUI where the operator controls all card metadata has little realistic risk; this is assessed as a medium-severity, low-priority issue in practice.

RemediationAI

No vendor-released patch for clarity-upscaler has been identified at time of analysis: the maintainers were contacted early through https://github.com/philz1337x/clarity-upscaler/issues/72 and have not responded, and because the project is a rolling release there is no tagged fixed version to upgrade to. The authoritative fix therefore exists only upstream in AUTOMATIC1111/stable-diffusion-webui v1.8.0 (March 1, 2024), so the practical remediation is to port or cherry-pick that upstream escaping change into modules/ui_extra_networks.py (specifically adding proper HTML output encoding of the Description value in create_html_for_item) or to rebase the fork onto v1.8.0 or later; until that is done, the code path must be treated as unfixed. Actionable compensating controls, with trade-offs, are: strip or delete untrusted card metadata (Description fields and accompanying .civitai.info / JSON sidecar files) from third-party models, LoRAs and embeddings before they are scanned by Extra Networks - this removes the injection vector but destroys the descriptive metadata users see in the UI; avoid loading third-party model files altogether on shared instances, which is the most reliable mitigation but limits the instance's usefulness; and restrict access so that only a single trusted operator can reach the WebUI (bind to localhost, do not enable --share or --listen on untrusted networks, and place the service behind an authenticating reverse proxy), which eliminates the multi-user exploitation path but does not help a multi-tenant deployment by design. Because the flaw requires a second user to view the poisoned card, isolating the instance to one trusted user neutralizes the realistic attack scenario even without a code fix.

Affected VersionsENISA

clarity-upscaler cfbdb842c6c839c8e97741722b8cf9a4b7662d98

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a CWE-79 improper-neutralization-of-input-during-web-page-generation (cross-site scripting) bug in the Extra Networks card rendering component of a Stable Diffusion WebUI fork. The function create_html_for_item in modules/ui_extra_networks.py builds the HTML card markup for locally discovered models, LoRAs, embeddings and other extra networks, and the Description attribute taken from model card metadata is inserted into that markup without proper output encoding. Because the input comes from persisted model metadata rather than a one-off request parameter, the resulting payload is stored and executed each time a victim loads the Extra Networks panel, which is why the assessed vector requires passive user interaction (UI:R/UI:P) and a low-privileged authenticated actor (PR:L) able to place or influence a card's Description. The affected product is identified by CPE cpe:2.3:a:philz1337x:clarity-upscaler:*:*:*:*:*:*:*:*, wildcarded because clarity-upscaler uses a rolling release model and publishes no fixed affected/updated version numbers; all repository snapshots up to commit cfbdb842c6c839c8e97741722b8cf9a4b7662d98 inherit the vulnerable rendering code from AUTOMATIC1111/stable-diffusion-webui v1.7.0. Scope is changed in the assessed CVSS 3.1 vector (S:C) with low confidentiality and integrity impact (C:L/I:L) and no availability impact, consistent with script execution confined to the victim's browser context.

Know when Clarity Upscaler 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

Vendor (VulDB) PRIMARY 5.1 MEDIUM
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
vuln.today AI 5.4 MEDIUM

Stored XSS requires a low-privileged user to inject the Description and a victim to view the card (UI:R), with script executing cross-context in the victim browser (S:C) for limited C/I impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
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

DescriptionCVE.org

A security flaw has been discovered in philz1337x clarity-upscaler up to cfbdb842c6c839c8e97741722b8cf9a4b7662d98. This impacts the function create_html_for_item of the file modules/ui_extra_networks.py of the component Extra Networks Card Rendering. The manipulation of the argument Description results in cross site scripting. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. All versions in the repository are affected, as the codebase is based on AUTOMATIC1111/stable-diffusion-webui v1.7.0 code. Upstream AUTOMATIC1111/stable-diffusion-webui (v1.8.0, released March 1, 2024) contains the fix. The project was informed of the problem early through an issue report but has not responded yet.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche open-source AI image upscaler, limited production deployment footprint
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy