Description
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.
Published: 2026-08-24
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Remote JavaScript Execution via Stored XSS
Action: Patch Now
AI Analysis

Impact

RansomLook stores cryptocurrency addresses and blockchain names directly in a database field that is later rendered in an inline JavaScript onclick handler on the wallet detail page. This is a Stored XSS vulnerability, classified as CWE-79. The input is not validated and the Jinja template engine’s autoescaping does not protect against script injection when the data is used inside a JavaScript string. As a result a malicious address containing quote characters and JavaScript syntax can break out of the string literal and execute arbitrary code when a user clicks the CSV export button. If executed, the attacker’s script runs in the RansomLook web application context, enabling disclosure of sensitive data, session hijacking, or other actions with the victim’s privileges.

Affected Systems

The vulnerable product is RansomLook. The vendor is identified as ransomlook, and the product is referred to simply as RansomLook. No specific version or release information was provided in the CVE record, so the risk applies to all deployments that use the software before the issued patch.

Risk and Exploitability

The CVSS 8.8 score suggests that a successful exploitation could lead to a wide range of attack outcomes, from data theft to defacement. In absence of active exploitation data, administrators should treat the vulnerability as a high‑priority threat due to the potential impact and ease of deployment via external inputs.

Generated by OpenCVE AI on August 24, 2026 at 20:05 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the vendor‑issued patch that validates all cryptocurrency addresses and blockchain identifiers before storage, limiting them to a safe character set. The patch also replaces inline JavaScript event handlers with data‑* attributes and an external event listener, ensuring that wallet values are treated strictly as data.
  • If a patch cannot be applied immediately, remove or disable the CSV export button on the wallet detail page to eliminate the direct execution path for the vulnerable script. Consider disabling the external data feed for wallet records or sanitizing any data imported from that source. This will prevent malicious addresses from being stored and later executed.
  • Implement a Content Security Policy that blocks inline JavaScript execution and requires all script content to be loaded from trusted origins. This mitigates the impact of any residual XSS payloads that may still be present before the patch is deployed.

Generated by OpenCVE AI on August 24, 2026 at 20:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 24 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Ransomlook
Ransomlook ransomlook
Vendors & Products Ransomlook
Ransomlook ransomlook

Mon, 24 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 24 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Description 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 &#39; 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.
Title Stored Cross-Site Scripting via Untrusted Cryptocurrency Address Rendering in RansomLook
Weaknesses CWE-79
References
Metrics cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Ransomlook Ransomlook
cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-08-24T15:08:14.815Z

Reserved: 2026-08-24T14:13:16.930Z

Link: CVE-2026-78391

cve-icon Vulnrichment

Updated: 2026-08-24T15:08:09.903Z

cve-icon NVD

Status : Deferred

Published: 2026-08-24T15:16:48.717

Modified: 2026-08-26T16:49:18.760

Link: CVE-2026-78391

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-24T20:15:04Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')