Stored Cross-Site Scripting via Untrusted Cryptocurrency Address Rendering in RansomLook
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · High
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
RansomLook contains a stored cross-site scripting (XSS) vulnerability in the cryptocurrency wallet detail view. Cryptocurrency addresses and blockchain names originating from external sources, including the public crowd-sourced ransomwhe.re feed, were stored without sufficient validation and later embedded directly into an inline JavaScript onclick handler. Although Jinja HTML autoescaping was applied, it does not provide adequate protection when untrusted data is inserted into a JavaScript string inside an HTML attribute. HTML entities such as ' are decoded by the browser's HTML parser before the resulting attribute is interpreted as JavaScript. Consequently, a specially crafted cryptocurrency address containing quote characters and JavaScript syntax could escape the intended string literal and execute arbitrary JavaScript when a user clicked the affected wallet's CSV export button. Because cryptocurrency information imported from an untrusted upstream could reach the vulnerable rendering path, exploitation may not require an authenticated RansomLook account if an attacker can introduce a malicious wallet record into a consumed external data source. Successful exploitation could allow attacker-controlled JavaScript to execute in the security context of the RansomLook web application, potentially exposing information accessible to the victim or performing actions with the victim's privileges. The patch mitigates the issue by validating cryptocurrency addresses and blockchain identifiers before storage, restricting them to a safe character set, and replacing the inline JavaScript handler with data-* attributes and an external event listener so wallet values are treated strictly as data rather than executable JavaScript.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| ransomlook | ransomlook | up to 2.0.0 | — | No fix listed | CNA |
- ransomlook Vendorransomlook Affected up to 2.0.0 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-78391
- 2026-10-03 Alias added: GHSA-mp5g-mcx2-r5xh
References
More ransomlook vulnerabilities
- TI-2026-54504 RansomLook Missing Authorization Allows Disclosure of Private Group and Ransom Note Data CVSS 4.0CRITICAL 9.2
- TI-2026-54503 RansomLook Unauthenticated Database Export Exposes Private Data CVSS 4.0CRITICAL 9.2
- TI-2026-54619 RansomLook Login Endpoint Allows Timing-Based Username Enumeration and Unthrottled Authentication Attempts CVSS 4.0HIGH 8.8
- TI-2026-54502 Missing Authentication Allows Unauthorized Creation of Crypto Groups in RansomLook CVSS 4.0HIGH 8.8
- TI-2026-54622 RansomLook API Key Disclosure Through /admin/apikeys HTML Source CVSS 4.0CRITICAL 9.4
- TI-2026-54516 RansomLook Missing Authorization in Web Configuration Editor Allows Application Configuration Modification CVSS 4.0CRITICAL 9.4
Sources
- CVE-2026-78391 · CVE Program
- CVE-2026-78391 · NVD
- FIRST EPSS
- GHSA-mp5g-mcx2-r5xh · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences