Cross-Site Scripting (XSS) in Lookyloo (CVE-2025-66460)
Summary
Cross-site scripting in Lookyloo (CVE-2025-66460). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.35.3 or later.
Original description
The description as published by the source.
Lookyloo is a web interface that allows users to capture a website page and then display a tree of domains that call each other. Prior to 1.35.3, Lookyloo passed improperly escaped values to cells rendered in datatables using the orthogonal-data feature. It is definitely exploitable from the popup view, but it is most probably also exploitable in many other places. This vulnerability is fixed in 1.35.3.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-66460 has been found in Lookyloo.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade Lookyloo to 1.35.3 or later.
If unsure, ask your IT team or search "Lookyloo CVE-2025-66460" on the vendor's site.
CVE-2025-66460 (Lookyloo) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.35.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Lookyloo.
Check the vendor advisory for the affected versions of Lookyloo.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 1.35.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Lookyloo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Lookyloo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Lookylooを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Lookyloo to 1.35.3ステージング環境で 1.35.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。