CVE-2026-56263 Crawl4AI - Stored Cross-Site Scripting in Monitor Dashboard
Attackers can inject malicious scripts into the Crawl4AI monitor dashboard, executing code in operators' browsers to potentially hijack sessions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-56263?
CVE-2026-56263 is a medium-severity cross-site scripting vulnerability in Crawl4AI, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-79
Which versions are affected by CVE-2026-56263?
It affects 1 product.
Products include Kidocode Crawl4ai.
How do I fix CVE-2026-56263?
Upgrade to a fixed version.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-56263 being exploited?
There is no known exploitation of CVE-2026-56263 in the wild and no public exploit code.
Other vulnerabilities in Crawl4AI
- CVE-2026-57572 Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args
- CVE-2026-26216 Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter
- CVE-2026-53753 Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API
- CVE-2026-57571 Crawl4AI arbitrary file write via download filename path traversal
- CVE-2026-56265 Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key