[Limited Spots] Join the AI Agent Security Evening with Cybersecurity Leaders. Reserve your seat->

Find your API Security Test

Jumpstart your API Security testing with our pre-built YAML tests. A library of 100+ API Security tests and growing everyday

Search…

Server Side Request Forgery (SSRF)

Clear filter

server-side-request-forgery

Sensitive files exposed due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with popular sensitive file paths. The application responded with 2XX success code and also gave out details of these files.

server-side-request-forgery

Port scanning with SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with some of the popular ports. The application responded with 2XX success code indicating that the port is open.

server-side-request-forgery

Sensitive AWS details exposed via replacing url param with encoded url due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with metadata endpoint provided by AWS in enclosed alphanumerics. The application responded with 2XX success code and also gave out sensitive AWS information in response.

server-side-request-forgery

Sensitive AWS details exposed due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with metadata endpoint provided by AWS. The application responded with 2XX success code and also gave out sensitive AWS information in response.

server-side-request-forgery

Sensitive AWS details exposed via replacing CSV param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing CSV upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

server-side-request-forgery

Sensitive AWS details exposed via replacing file param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing file parameter with sensitive file path. The application responded with 2XX success code and also gave out sensitive AWS information in response.

server-side-request-forgery

Sensitive AWS details exposed via replacing image param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing image upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

server-side-request-forgery

Sensitive localhost details exposed via replacing URI param with localhost/admin due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin. The application responded with 2XX success code and also gave out admin-related details.

server-side-request-forgery

Sensitive localhost details exposed via replacing URI param redirecting to localhost/admin due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin. The make-127-0-0-1-rr.1u.ms/admin which redirects to localhost/admin.

server-side-request-forgery

Sensitive localhost details exposed via replacing URI param to encoded localhost/admin due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin in an encoded format. The application responded with 2XX success code and also gave out admin-related details.

server-side-request-forgery

Sensitive AWS details exposed via replace PDF param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing PDF upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

server-side-request-forgery

Sensitive AWS details exposed via replacing XML param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing XML upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

Read our blog

Agentic AI Security

4 Minutes

Agentic AI Security Framework: A Stepwise, Technical Guide for 2026

Agentic AI Security

3 Minutes

OpenClaw AI Agent Security Risks: Technical Deep Dive and Modern Defenses