> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Check for server-side request forgery (SSRF) in URL previews, remote imports, and other features that fetch content on the server.

# SSRF testing for web applications


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

An application server can reach services its users cannot. Server-side request forgery (SSRF) occurs when the application makes an unintended request on a user's behalf, potentially crossing a protected network boundary.

This scenario applies to features that fetch remote content on the server. Common examples include link previews, image imports, and imports from a URL. The assessment focuses on the boundaries your service is meant to enforce for those requests.

A finding identifies the affected feature and what the report observed about the request. For the source-code view of this boundary, see [outbound request boundaries in code](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-server-request-boundaries).

The app lists this scenario as **Use server-side fetching to cross a network boundary** (`APP-13`) in [Application Red Teaming](https://www.superagent.sh/docs/products/red-teaming/applications).

## Standards and guidance

[CWE-918 Server-Side Request Forgery (SSRF)](https://cwe.mitre.org/data/definitions/918.html)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/application-server-fetch-boundaries
Index: https://www.superagent.sh/llms.txt
