hackXpert labs
All labs › SSRF

📡 SSRF

Anywhere the server fetches a URL for you, it is also willing to fetch one for itself. Webhooks, importers, PDF renderers, link previews.

4 labs and targetsfree, no accountlesson included
How request forgery actually works — taught by The XSS Rat

What it is

CSRF abuses the browser's habit of attaching credentials to any request to a site, so a page you control can act as the victim. SSRF abuses the server's position inside the network, turning it into your proxy to things you cannot reach from outside.

How I attack it

  1. For CSRF: strip the token and see if the endpoint still accepts the request. Then try a wrong token, an empty token, and another user's token.
  2. Check the method and content type - plenty of JSON endpoints happily accept a form post.
  3. For SSRF: anywhere the app fetches a URL is a candidate - webhooks, importers, PDF renderers, image proxies, link previews.
  4. Prove impact beyond a callback: cloud metadata, internal admin panels, ports that should not be reachable.

Learn it from The XSS Rat

Free reference reading

The set 4

SSRF example

The basic shape: a fetcher that takes a URL from you.

API SSRF

A JSON API that takes a callback URL.

Also here 2

Nothing matches thatClear the filter to see everything again.