CVE-2025-3192: Versions of the package spatie/browsershot from 0.0.0 are vulnerable to Server-side Request Forgery (SSRF)...
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-3192 is an SSRF issue in the PHP package spatie/browsershot. If an application lets users influence the URL passed to setUrl(), an attacker may make the server request localhost resources and expose directory listings. This matters most for applications using Browsershot to render user-supplied URLs.
Executive priority
Treat as high priority for applications that render user-submitted URLs or screenshots. The business risk is unauthorized access to local or internal resources from the application server. Prioritize inventory and containment while checking vendor guidance for fixes.
Technical view
The issue is CWE-918 in spatie/browsershot setUrl(), caused by missing restriction on user input. The CVE describes access to localhost and listing local directories. CVSS v4.0 is 8.8 high with network attack, low complexity, no privileges, and no user interaction. The provided data does not identify a fixed version.
Likely exposure
Exposure is likely limited to PHP applications using spatie/browsershot where untrusted users can control or influence setUrl() input. Internal-only uses with fixed, trusted URLs are less exposed, but should still be reviewed.
Exploitation context
The CVSS vector marks exploit maturity as proof-of-concept, and a public gist is referenced. The CVE is not listed as KEV in the provided bundle, so active exploitation is not established by these sources.
Researcher notes
Source data is incomplete on affected version ranges and fixes. The bundle states versions from 0.0.0 are vulnerable, but does not name a patched release. Avoid assuming all deployments are exploitable; exploitability depends on application-level exposure of setUrl() to untrusted input.
Mitigation direction
Check Snyk and upstream vendor guidance for a patched or recommended version.
Do not pass untrusted user-controlled URLs directly into setUrl().
Restrict Browsershot access to localhost and internal network destinations where feasible.
Add allowlists for expected URL schemes, hosts, and paths.
Prioritize review of internet-facing rendering or screenshot features.
Validation and detection
Inventory applications using the spatie/browsershot Composer package.
Identify code paths calling setUrl().
Determine whether users can influence setUrl() values.
Review controls blocking localhost and internal network access.
Check dependency advisories for available fixed versions or vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.