# 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.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **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:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 14 Jul 2026

## 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 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-56263?

It affects 1 product.


Products: Kidocode Crawl4ai.

## How do I fix CVE-2026-56263?

Upgrade to a fixed version.

## 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](https://insights.sbomify.com/CVE-2026-57572/): Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args (critical 10.0)
- [CVE-2026-26216](https://insights.sbomify.com/CVE-2026-26216/): Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter (critical 10.0)
- [CVE-2026-53753](https://insights.sbomify.com/CVE-2026-53753/): Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API (critical 9.8)
- [CVE-2026-57571](https://insights.sbomify.com/CVE-2026-57571/): Crawl4AI arbitrary file write via download filename path traversal (critical 9.6)
- [CVE-2026-56265](https://insights.sbomify.com/CVE-2026-56265/): Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56263 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-56263 in the wild and no public exploit code.

Affected product: Crawl4AI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56263/ (Markdown: https://insights.sbomify.com/CVE-2026-56263/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56263
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56263
- OSV: https://osv.dev/vulnerability/CVE-2026-56263

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56263/
Summaries are generated and may contain mistakes; the official description above is the record.