thanks Ed for helping the community.
On Wed, Jul 4, 2018 at 7:53 PM Edwin <contact@xxxxxxxxxxxxxx> wrote:
In that case, just report it as is or look at other issues that may allow
you as an external hacker to exploit the issue against an authenticated
user (e.g. clickjacking, priviledge escalation, etc.)
On Wed, Jul 4, 2018 at 7:48 PM, Sawzeeyy <iamsawzy@xxxxxxxxx> wrote:
Totally helpful but I thought that through during a current finding but
both vulnerabilities weren't present. What to do?
On Wed, Jul 4, 2018 at 6:30 PM Edwin <contact@xxxxxxxxxxxxxx> wrote:
If you have found an authenticated stored XSS vulnerability that requires
specific permissions to exploit — say administrator-level access —
*always* check to see if the POST request that transmitts the payload is
vulnerable to CSRF or an IDOR. This will increase the impact, since as an
attacker you no longer need an account with certain permissions to exploit
I cannot count the number of times that I have received reports and the
hacker hadn't verified this. In two cases recently, I helped escalate the
reports from $300 to $1.5k.