CVE-2026-45231: DumbAssets 1.0.11 Stored Cross-Site Scripting via Asset Fields
DumbAssets through 1.0.11 contains a stored cross-site scripting vulnerability in asset fields including name, description, modelNumber, serialNumber, and tags that are stored without server-side sanitization and rendered using innerHTML without client-side escaping. Attackers can create or update assets with HTML or JavaScript payloads via the asset API endpoints to execute arbitrary scripts in the browsers of users viewing the asset list, and with Content-Security-Policy disabled, the injected scripts can make unrestricted connections to internal network services.
Security readout for executives and security teams
Plain-English summary
DumbAssets through 1.0.11 can store unsafe content in asset fields. When another user views the asset list, that content may run in their browser. This is a moderate business risk because it can expose user sessions or data shown in the application, especially where DumbAssets is reachable by untrusted users.
Executive priority
Treat as a moderate remediation item. Prioritize systems exposed to the internet, used by many staff, or lacking CSP. The main risk is browser-side compromise of users who view malicious asset records, not direct server takeover based on the provided sources.
Technical view
CVE-2026-45231 is stored XSS in DumbAssets asset fields including name, description, modelNumber, serialNumber, and tags. The data is stored without server-side sanitization and rendered with innerHTML without client-side escaping. The CVSS 3.1 score is 6.1, with network attack vector, low complexity, user interaction required, and changed scope.
Likely exposure
Organizations using DumbWareio DumbAssets through 1.0.11 are potentially exposed, especially if asset creation or update API endpoints are reachable by unauthenticated or untrusted users. The provided sources do not identify other affected products or a confirmed fixed release.
Exploitation context
The source bundle does not report active exploitation and KEV is false. Exploitation requires a user to view a poisoned asset list after malicious content is stored. Sources note that disabled Content-Security-Policy increases impact by allowing injected scripts to connect to internal services.
Researcher notes
Evidence supports stored XSS in multiple asset fields and unsafe rendering. Patch availability is not clearly established in the provided bundle, so avoid assuming a fixed version. Validate exposure through version inventory, route access review, CSP configuration, and data inspection without using weaponized payloads.
Mitigation direction
Check DumbAssets vendor guidance and PR #135 for the official fix status.
Upgrade when the vendor publishes or confirms a fixed release.
Restrict untrusted access to asset create and update endpoints.
Enable a restrictive Content-Security-Policy for scripts and connection destinations.
Remove unsafe HTML or script content from existing asset fields.
If maintaining a fork, sanitize input and escape output before rendering.
Validation and detection
Inventory DumbAssets deployments and confirm whether versions through 1.0.11 are present.
Review named asset fields for unexpected HTML or script content.
Inspect the asset list rendering path for unsafe innerHTML usage.
Confirm CSP is enabled and restricts script execution and outbound connections.
Review asset creation and update logs for suspicious activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.