CVE-2025-3192: 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.
Other sources
Versions of the package spatie/browsershot from 0.0.0 to 5.0.3 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.
— GitHub
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
spatie/browsershotto a version that resolves this vulnerability.Fixed in 5.0.3 - Compensating control
Ensure user input passed to spatie/browsershot setUrl() is restricted/validated so it cannot be used to access localhost or perform directory listing (SSRF mitigation).
Event History
Frequently Asked Questions
What is the severity of CVE-2025-3192?
CVE-2025-3192 has a medium severity due to its potential for Server-side Request Forgery (SSRF) vulnerabilities.
How do I fix CVE-2025-3192?
To fix CVE-2025-3192, update the Spatie Browsershot package to a version that mitigates this vulnerability.
What versions are affected by CVE-2025-3192?
CVE-2025-3192 affects all versions of the Spatie Browsershot package starting from 0.0.0.
What type of attack does CVE-2025-3192 allow?
CVE-2025-3192 allows for Server-side Request Forgery (SSRF) attacks that enable access to localhost and its directories.
Is user input properly validated in CVE-2025-3192?
No, CVE-2025-3192 is due to a lack of restriction on user input in the setUrl() function.