CVE-2025-57818

What it is

Firecrawl turns entire websites into LLM-ready markdown or structured data. Prior to version 2.0.1, a server-side request forgery (SSRF) vulnerability was discovered in Firecrawl's webhook functionality. Authenticated users could configure a webhook to an internal URL and send POST requests with arbitrary headers, which may have allowed access to internal systems. This has been fixed in version 2.0.1. If upgrading is not possible, it is recommend to isolate Firecrawl from any sensitive internal systems.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-08-26 18:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 09:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-08-26 18:15 UTC

Last modified

2026-06-17 09:43 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-918 · Server-side request forgery

Record status

Deferred

Attack profile CVSS 3.1 · 6.3

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-57818.md and follow it. Check whether this project is affected by CVE-2025-57818. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge