user avatar
Web Security Academy
@WebSecAcademy
Free web security training from @PortSwigger
  • user avatar
    What is HTTP Downgrading, why use it, and how does it work? HTTP/2 is default for most web apps these days, however, it's not uncommon for backend servers to still use HTTP/1.1 causing parsing mismatches between frontend and backend. And that's where HTTP downgrading comes in!
    00:00
  • user avatar
    How to deliver reflected XSS via HTTP request smuggling vulnerability! 👇 Try this Practitioner lab now: portswigger.net/web-security/r…
    00:00
  • user avatar
    We’ve added a brand new topic on insecure deserialization, with 10 new labs. portswigger.net/web-security/d…
  • user avatar
    Who wants to win a @Burp_Suite hoodie? We'll be launching a brand new Web Security Academy topic later today, including 13 new labs. portswigger.net/web-security
  • user avatar
    The Web Security Academy already covers XSS, SQLi, CSRF, SSRF, XXE, OS command injection, directory traversal., and HTTP request smuggling. We’ll be adding more topics very soon. portswigger.net/web-security
  • user avatar
    How to use Burp Suite's "Decoder" for URL-encoding. (plus a much easier way to do it)
    00:00
  • user avatar
    Our brand new XSS cheat sheet is now live, with hundreds of modern vectors, developed by @garethheyes portswigger.net/web-security/c…
  • user avatar
    We've added a huge new topic, on XXE (XML external entity) injection. Lots of new content and 9 new labs! portswigger.net/web-security/x…
  • user avatar
  • user avatar
    How to manually check for CL.TE Request Smuggling Vulnerabilities: 1️⃣ See if a GET request accepts POST 2️⃣ See if it accepts HTTP/1 3️⃣ Disable "Update Content-Length" 4️⃣ Send with CL & TE headers: POST / HTTP/1.1 Host: <HOST-URL> Content-Length: 6 Transfer-Encoding: chunked 0
    00:00
  • user avatar
    We've added a topic on HTTP request smuggling. There are 12 labs where you can learn about this brand new vulnerability. portswigger.net/web-security/r…
  • user avatar
    HTTP Request Smuggling Lab Walkthrough: Confirming a CL.TE vulnerability via differential responses. How to identify CLTE Vulnerabilities: 1. Send request to repeater 2. Downgrade protocol to HTTP/1.1 3. Disable "Update Content-Length" 4. Set Content-Length to 6 5. Add
    00:00
  • user avatar
    We've added a brand new topic, on SSRF (server-side request forgery). New learning content and labs. Have fun! portswigger.net/web-security/s…
  • user avatar
    We've added a brand new topic on testing for #WebSockets vulnerabilities, including three new labs. portswigger.net/web-security/w…