PYSEC-2026-230: Crawl4AI - Stored Cross-Site Scripting in Monitor Dashboard
Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /crawl/job and /llm/job endpoints, which accept webhook URLs without destination validation. An attacker can supply webhook URLs pointing to private or internal IP ranges, Docker networks, or cloud metadata endpoints (e.g. 169.254.169.254), causing the server to make requests to internal services and potentially expose cloud metadata.
Other sources
Crawl4AI before 0.8.7 contains a server-side request forgery vulnerability in the /crawl, /crawl/stream, /md, and /llm endpoints that fetch arbitrary user-supplied URLs without validation. Unauthenticated attackers can bypass the internal-address blocklist using IPv6-mapped IPv4 addresses to reach internal services and cloud metadata endpoints.
— OSV
Crawl4AI before 0.8.7 contains a stored cross-site scripting vulnerability in the monitor dashboard that renders crawl URLs and error messages via innerHTML without escaping. An attacker can submit a crafted crawl request with malicious markup that executes in an operator's browser when viewing the dashboard.
— OSV
Crawl4AI before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The outputpath parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location writable by the application's user, overwriting server files and causing denial of service.
— OSV
Crawl4AI before 0.8.7 contains an arbitrary JavaScript execution vulnerability in the Docker API server's /executejs endpoint, which accepts and executes arbitrary user-supplied JavaScript in the server's browser context with --disable-web-security enabled. An attacker can execute arbitrary JavaScript and, combined with the browser's relaxed security settings, perform server-side request forgery against internal services.
— OSV
Crawl4AI before 0.8.7 contains an authentication bypass vulnerability due to a hardcoded default JWT signing key in the Docker API server. Attackers who know the default key can forge valid authentication tokens for any user, bypassing authentication and gaining full access to protected functionality.
— OSV
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Crawl4AIto a version that resolves this vulnerability.Fixed in 0.8.7
Event History
Frequently Asked Questions
Which deployments are exposed to the stored XSS issue?
Crawl4AI versions before 0.8.7 are affected. The issue is in the monitor dashboard, which renders crawl URLs and error messages without escaping them.
What does an attacker need to trigger the dashboard XSS?
An attacker needs to submit a crafted crawl request containing malicious markup. When an operator later views the affected content in the monitor dashboard, the markup executes in that operator's browser.
Are unauthenticated users relevant to the related SSRF exposure?
Yes. The /crawl, /crawl/stream, /md, and /llm endpoints can be reached by unauthenticated attackers, who can use IPv6-mapped IPv4 addresses to bypass the internal-address blocklist and target internal services or cloud metadata endpoints.
Which endpoints accept unvalidated webhook destinations?
The Docker API server's /crawl/job and /llm/job endpoints accept webhook URLs without destination validation. These URLs can point to private or internal ranges, Docker networks, or cloud metadata addresses such as 169.254.169.254.