# CVE-2025-3192: Browsershot Server-Side Request Forgery (SSRF) via setURL() Function

> Attackers can exploit missing input restrictions in setUrl() to perform SSRF, accessing localhost and listing directories.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2025
- **Updated:** 2 Aug 2026
- **Also known as:** CLSA-2026-1771289500, CLSA-2026-1771289503, GHSA-qw64-6vcc-8ghx

## What is CVE-2025-3192?

CVE-2025-3192 is a high-severity server-side request forgery vulnerability in spatie/browsershot, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of the package spatie/browsershot from 0.0.0 are vulnerable to Server-side Request Forgery (SSRF) in the setUrl() function due to a missing restriction on user input, enabling attackers to access localhost and list all of its directories.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-3192?

2 open source packages ship an affected version, including spatie/browsershot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spatie/browsershot` | Packagist | All versions to 5.0.3 | None |
| `spatie/browsershot` | Packagist | All versions to 5.0.3 | None |

## How do I fix CVE-2025-3192?

Upgrade to a fixed version.

## Is CVE-2025-3192 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3192 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3192 and fix it if it is affected.

What it is: CVE-2025-3192 is a high-severity server-side request forgery vulnerability in spatie/browsershot, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3192 exists.

Affected packages and fixed versions:
- spatie/browsershot (Packagist): affected all versions up to 5.0.3; no fix listed
- spatie/browsershot (Packagist): affected all versions up to 5.0.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3192/ (Markdown: https://insights.sbomify.com/CVE-2025-3192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3192
- OSV: https://osv.dev/vulnerability/CVE-2025-3192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3192/
Summaries are generated and may contain mistakes; the official description above is the record.