Updated readme

README.md

@@ -19,3 +19,33 @@ Some of the files are plain JavaScript .js files, others are PHP scripts which s
 * You can't serve these over HTTP if your app is running on HTTPS. You'll need to serve them over HTTPS
 * If you're running these over HTTPS for actual exploitation rather than a PoC, you'll need a proper trusted TLS cert (Let's Encrypt CA, for example) otherwise victim's browsers won't fetch the files at all. If it's for a PoC you can just temporarily trust your self signed cert.
 * Hit F12 and view the debug console for any information about why a particular script might not work
+
+## Payloads
+
+### apache_httponly_bypass.js
+
+Uses an excessively large cookie to exploit CVE-2012-0053 and extract HTTPOnly cookie values from the response.
+
+### contentstealer.php
+
+Steal the content of the current page, a specific element or another page within the same origin as the exploited web app.
+
+### cookiestealer.php
+
+Steal cookies from the site.
+
+### formsubmitter.php
+
+Grab a page from somewhere within the same origin, fill in a form on it and then submit that form.
+
+### local_network_scan.php
+
+Get the internal IP address of a victim and then have them do a TCP port scan of common ports on the /24 of that internal IP address.
+
+### loginpage.php
+
+Pop up a login page which sends the entered credentials back to this URL.
+
+### unc_hashstealer.php
+
+Fire up Responder.py on the same host as this script and then inject this payload. All links on the injected page will be turned into UNC paths to the same host.