Crawl4AI 0.9.0 before 0.9.5 JavaScript Injection via css_selector and wait_for
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.9.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Crawl4AI, a web crawling tool, is affected through its Docker API server, where authenticated API clients can inject JavaScript into crawled pages via the css_selector and wait_for request fields. This allows attackers to run arbitrary scripts that can alter page state and change the crawl content returned to them.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Crawl4AI from 0.9.0 before 0.9.5 contains a JavaScript injection vulnerability in the Docker API server that allows authenticated API clients to run arbitrary JavaScript in the crawl page via allowlisted css_selector and wait_for fields. Attackers can inject quotes into css_selector or supply js: conditions in wait_for, bypassing the js_code block to alter page state and returned crawl content.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- unclecode crawl4ai
From 0.9.0 · fixed in 0.9.5