Skip to main content
VulnerabilityPublished Updated

CVE-2026-91944: unclecode crawl4ai · Cross-site Scripting

Affects unclecode crawl4aiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 0.9.3 when convenient.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade crawl4ai and unclecode/crawl4ai to 0.9.3.

Affected software

ProductAffectedFixed in
unclecodecrawl4aiAffected
  • <0.9.3
Fixed in
  • 0.9.3
GitHubunclecode/crawl4aipkg:github/unclecode/crawl4aiOther threatsAffected
  • <0.9.3
Fixed in
  • 0.9.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in crawl4ai version 0.9.3. Users should upgrade to version 0.9.3 or later to remediate this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes.

Description

crawl4ai versions before 0.9.3 contain a DOM-based cross-site scripting vulnerability in the Playground UI where the forceHighlightElement() function assigns textContent back to innerHTML, re-parsing JSON responses as HTML. Attackers can inject malicious scripts through crawled page content like the page title to steal the operator's API token from sessionStorage and gain full server control.

References

Community reviews

Loading reviews…