Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged user
-
DeliveryUpload SVG/HTML via uploadlogo endpoint
-
ExploitSpoof image MIME type to bypass check
-
ExecutionFile served unauthenticated from /assets/
-
PersistVictim browser loads branding and executes script
-
ImpactHijack session or deface instance branding
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated Trudesk account of any privilege level (PR:L) with access to the Settings > General branding upload functionality, specifically the uploadlogo, uploadpagelogo, and uploadfavicon endpoints. The attacker must spoof an image MIME type so a script-bearing HTML or SVG file passes the image check, after which the file is served unauthenticated from /assets/. Exploitation is limited by three factors: it is not unauthenticated (an account is required), the stored-XSS payload only fires when a victim passively loads a page referencing the uploaded branding asset (UI:P), and it affects Trudesk instances running version 1.2.11 or earlier in their default self-hosted configuration. |
| Impact | This is a genuine but moderate-priority issue, consistent with its CVSS 4.0 base score of 5.1 (medium). The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P) indicates a network-reachable, low-complexity flaw that nevertheless requires authentication (PR:L) and passive victim interaction (UI:P) for the stored-XSS payload to execute - both of which meaningfully temper real-world risk. Impact is limited: no confidentiality or availability impact on the vulnerable system (VC:N/VA:N) and only low integrity impact (VI:L, i.e., branding replacement), with low subsequent-system impact (SC:L/SI:L) reflecting script execution in other users' browsers. No EPSS score, SSVC decision, or KEV entry was provided, so exploitation-probability signals are absent rather than low - this should not be read as 'safe,' only as 'unmeasured.' Exploitation status is 'no public exploit identified at time of analysis' per the supplied signals, though a detailed third-party technical writeup (hackmd) and source-line references exist, which lowers the barrier to developing a working exploit. Net: a real, authenticated stored-XSS/defacement bug worth patching, but not an emergency - the authentication and user-interaction requirements, plus niche product footprint, keep it below critical-priority thresholds. |
| Exploit ScenarioDerived | A low-privileged authenticated Trudesk user uploads an SVG or HTML file carrying JavaScript through the Settings > General logo/favicon upload endpoints, spoofing an image MIME type to bypass validation. The file lands in the public webroot and is served unauthenticated from /assets/; when an administrator or another user loads a page referencing that branding asset, the stored script executes in their browser session. No public exploit code is identified at time of analysis, but a technical writeup describing the flaw is publicly available. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Stored cross-site scripting in Trudesk through 1.2.11 allows any authenticated user to upload script-bearing HTML or SVG files through the uploadlogo, uploadpagelogo, and uploadfavicon branding endpoints, which are then served unauthenticated from /assets/. Exploitation requires a valid low-privileged account (CVSS PR:L) and victim interaction when a page referencing the asset is loaded (UI:P); the impact is limited to integrity and cross-site scripting rather than remote code execution. No public exploit identified at time of analysis, and the CVSS 4.0 base score is 5.1 (medium).
RemediationAI
No vendor-released patch identified at time of analysis. Until an update is available, restrict access to Settings > General branding uploads to fully trusted administrators and audit existing logo, page-logo, and favicon assets for HTML or SVG content. Enforce server-side content validation instead of trusting the multipart Content-Type by decoding and re-encoding images, rejecting SVG/HTML/SVGZ uploads, and storing uploads outside the public webroot; note that blocking SVG may break legitimate branding. Configure the web server to serve /assets/ with X-Content-Type-Options: nosniff and Content-Disposition: attachment for non-image types, or host user-uploaded assets on a separate cookieless domain; these controls may affect normal image rendering if applied too broadly. Deploy a restrictive Content-Security-Policy (for example script-src 'self' without unsafe-inline and object-src 'none') to reduce stored-XSS impact, and monitor /assets/ for unexpected .html or .svg files. See https://www.vulncheck.com/advisories/trudesk-through-1.2.11-unrestricted-file-upload-via-settings-general-uploadlogo and https://hackmd.io/@leediay/multiple-vuln-trudesk-1211 for details.
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
CWE-434 (Unrestricted Upload of File with Dangerous Type) applies to Trudesk, a Node.js self-hosted helpdesk application. The vulnerable handlers are in src/controllers/main.js lines 612-837, reached through src/routes/index.js lines 293-295 for the uploadlogo, uploadpagelogo, and uploadfavicon settings actions. The code trusts the client-supplied MIME type rather than validating file content, so an authenticated user can label an HTML or SVG payload as image/png or image/jpeg and have it written into the public webroot. Because files under /assets/ are served without authentication, the HTML/SVG is rendered in the application origin and can execute script in the context of any user or administrator who views a page referencing the branding asset, enabling stored XSS and replacement of instance branding. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N) reflects network reachability, low privileges required, passive user interaction, no direct confidentiality or availability impact on the vulnerable component, and limited subsequent-system integrity/confidentiality impact; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) is consistent with a scope-changed stored-XSS issue rather than code execution.
Know when Trudesk 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:L/SI:L/SA:N
Network-reachable but requires a low-privileged account (PR:L) and victim page load (UI:R); stored XSS crosses into the victim's browser context (S:C) with low confidentiality and integrity impact and no availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Trudesk through 1.2.11 contains an unrestricted file upload vulnerability that allows any authenticated user to place HTML or SVG files in the public webroot via the uploadlogo, uploadpagelogo and uploadfavicon endpoints. Attackers can spoof an image MIME type to upload script-bearing files served unauthenticated from /assets/, enabling stored cross-site scripting and replacement of instance branding.
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.
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Unrestricted Upload of File with Dangerous Type in GitHub repository polonel/trudesk prior to 1.2.4. Rated critical seve
Incorrect Use of Privileged APIs in GitHub repository polonel/trudesk prior to 1.2.4. Rated critical severity (CVSS 9.8)
Weak Password Requirements in GitHub repository polonel/trudesk prior to 1.2.2. Rated critical severity (CVSS 9.8), this
Execution with Unnecessary Privileges in GitHub repository polonel/trudesk prior to 1.2.3. Rated high severity (CVSS 8.8
Improper Privilege Management in GitHub repository polonel/trudesk prior to 1.2.2. Rated high severity (CVSS 8.8), this
Incorrect Synchronization in GitHub repository polonel/trudesk prior to 1.2.3. Rated high severity (CVSS 8.1), this vuln
Unrestricted Upload of File with Dangerous Type in GitHub repository polonel/trudesk prior to 1.2.2. Rated high severity
The trudesk application allows large characters to insert in the input field "Full Name" on the signup field which can a
Improper Restriction of Rendered UI Layers or Frames in GitHub repository polonel/trudesk prior to 1.2.2. Rated medium s
Use of Incorrect Operator in GitHub repository polonel/trudesk prior to 1.2.3. Rated medium severity (CVSS 6.5), this vu
Integer Overflow or Wraparound in GitHub repository polonel/trudesk prior to 1.2.2. Rated medium severity (CVSS 6.5), th
Allowing long password leads to denial of service in polonel/trudesk in GitHub repository polonel/trudesk prior to 1.2.2
EUVD-2026-107245
GHSA-3469-653g-542x
NVD
CVE.org
EPSS
Exploit-DB