Disclosed weakness · no CVE recorded

OpenClaw could mix Firecrawl search and scraping credentials and destinations

OpenClaw · OpenClaw

First documented disclosure · Review checkpoint

Summary

Search and scraping could use connection settings belonging to the other Firecrawl operation.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The project documents the defect and its correction. The reviewed sources identify no malicious use or victim.

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The plugin did not consistently keep each operation’s credential paired with its configured service endpoint.

Conditions required

The operator uses distinct Firecrawl accounts, keys or endpoints for searching and scraping.

Potential impact

A service could receive a credential or query intended for the other scoped operation.

Affected versions and configurations

The project identifies the affected behavior. Its full version range is unverified.

Fix and mitigation status

OpenClaw 2026.11.3 includes the correction. An earlier fixed build may exist.

Practical next steps

Update to the fixed plugin build. Review destinations and credentials separately for search and scraping.

Operating lesson

Keep service credentials and destination settings together when assigning access to an agent tool.

Evidence and limits

The original public project discussion predates the November stable release. The reviewed sources give no CVE identity or CVSS score for this defect.

Sources