External risk intelligence

Lookyloo Cross-Site Scripting Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2025-65095

Lookyloo is designed as a web interface used to capture and analyze website pages. As a web application intended for interaction with external sites and typically hosted as an accessible service for users to perform these captures, it constitutes an internet-facing web application deployment.

Cross-site Scripting

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in Lookyloo, a web interface used for capturing and analyzing website pages. This issue could allow for cross-site scripting attacks, potentially impacting the integrity and confidentiality of data processed by the application. The primary concern is to confirm if this specific technology is in use within our environment.

  • Website analysis tool has a critical security flaw.
  • Potential for unauthorized access to website data.
  • Confirm usage and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by tricking a user into visiting a malicious link or by embedding a malicious link on a compromised website. When the user interacts with the vulnerable pages of Lookyloo, the attacker's injected script could be executed. This could lead to the attacker gaining access to sensitive information or performing unauthorized actions within the application.

  • Requires user interaction with a malicious link.
  • Triggered by visiting index or tree pages.
  • Potential for cross-site scripting attacks.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, this vulnerability could allow an attacker to inject malicious scripts into the web interface, impacting the display of domain relationships and potentially affecting user sessions.

  • Web interface data and service behavior.
  • Malicious scripts injected into pages.
  • Compromised user sessions and data.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Lookyloo application's web interface is likely managed by a platform or application team, with network and security teams responsible for its exposure and initial triage. The first practical step is to identify all Lookyloo instances, assess their reachability and business criticality, and then engage the accountable owner to plan remediation.

  • Platform or application team owns the issue.
  • Verify instance reachability and business criticality.
  • Plan remediation with accountable owner.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Lookyloo?

Lookyloo is an open-source web application designed to help researchers and analysts visualize the relationships between different web domains. When you provide a URL, it captures the page and generates a tree-like map showing which domains call or load content from others. Because it processes and displays external website data, it acts as a browser-based analysis tool for mapping complex web request chains.

What does CVE-2025-65095 mean?

This CVE identifies a Cross-Site Scripting (XSS) vulnerability, classified as CWE-79. In simple terms, the application fails to properly sanitize user-supplied data before displaying it on the index or tree pages. This weakness allows an attacker to inject and execute malicious scripts in a user's browser, enabling them to potentially hijack sessions or view data within the context of the Lookyloo interface.

How is this Lookyloo vulnerability triggered?

The flaw is triggered when a user visits a maliciously crafted link or interacts with specific components on the index or tree pages. The issue is specific to the web interface's handling of page data; simply running the underlying domain capture engine in the background does not trigger the execution of these malicious scripts. Execution requires active engagement through the vulnerable web interface.

Do I need to worry about this if my Lookyloo instance is internal?

Halo Surface Signal notes that Lookyloo is typically deployed as an internet-facing service for capturing external sites, which increases the likelihood of attack. Even if your instance is internal, the vulnerability remains a risk if unauthorized users can reach the web interface. You should evaluate who has access to the application and whether those users could be coerced into visiting malicious links that target the internal service.

When should I prioritize fixing this for my Lookyloo instance?

You should prioritize this immediately by identifying all deployed instances. Since the vulnerability is patched in version 1.35.1, the first practical step is to verify your current version. Work with the platform or application owner to schedule an update to 1.35.1 or later. If an immediate update is not possible, restrict access to the application as a temporary measure to limit potential exposure.

References