dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-56263

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 0.8.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Crawl4AI before 0.8.7 contains a stored cross-site scripting vulnerability in its monitor dashboard. The application renders crawl URLs and error messages using innerHTML without proper output encoding, allowing attackers to inject malicious HTML/JavaScript via crafted crawl requests that execute when dashboard operators view the data.

MitigationUpgrade to Crawl4AI version 0.8.7 or later which implements proper output escaping when rendering user-supplied crawl data in the dashboard. Until upgraded, restrict dashboard access to trusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Crawl4aiApplication
Affected:< 0.8.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Crawl4AI version
    Locate the Crawl4AI installation and determine its version number. This may be found in application logs, configuration files, or by querying the application directly. Compare the version against the affected range of versions before 0.8.7.
    Affected if The installed version is below 0.8.7
  2. Confirm dashboard is enabled
    Determine whether the monitor dashboard feature is active. Check if the dashboard endpoint is reachable and the application is configured to display crawl results through a web interface.
    Affected if The monitor dashboard is enabled and accessible
  3. Assess dashboard access controls
    Evaluate who can access the dashboard interface. Determine if authentication is required and whether untrusted users or external parties can reach the dashboard.
    Affected if The dashboard is accessible to untrusted or unauthenticated users
  4. Review stored crawl data
    Inspect the crawl history or database where URLs and error messages are stored. Look for any entries containing unexpected HTML tags, script elements, or JavaScript event handlers that may indicate malicious injection.
    Affected if Malicious HTML or script tags are present in stored crawl URLs or error messages

The environment is affected if Crawl4AI version is below 0.8.7 and the dashboard is accessible to users who could inject malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.8.7 or later
Fixed in 0.8.7
Interim mitigation

Upgrade to Crawl4AI version 0.8.7 or later which implements proper output escaping when rendering user-supplied crawl data in the dashboard. Until upgraded, restrict dashboard access to trusted users.

Recommended fix High confidence

0.8.7

  1. Verify current installed version of Crawl4AI by checking package metadata or docker image tag
  2. Backup any existing Crawl4AI configuration files, databases, or custom settings
  3. Upgrade Crawl4AI to version 0.8.7 or later using the appropriate installation method (e.g., pip install crawl4ai==0.8.7, docker pull crawl4ai:0.8.7, or git checkout v0.8.7)
  4. Restart the Crawl4AI service to apply the updated version
  5. Verify the new version is running and the dashboard is accessible
  6. Log into the monitor dashboard and confirm it renders URLs and error messages safely without executing injected scripts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crawl4ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56263 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56263 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data