New answers tagged

2

If the website is returning an SQL syntax error to you, then you definitely have found an SQLi vulnerability. You're not dealing with a WAF (sometimes it can be hard to tell the difference). It also means that, conveniently for you, he has error printing turned on. That makes it much easier to tell what is going on. That's also a vulnerability he should ...


3

Since you're confident that the SQL vulnerability exists based on your Burp results, I'm going to assume that you got that error message from your web client. Either your input has a type attribute set to email, either there's a JavaScript snippet which checks that your input matches an email address format. The easiest way to bypass both of these checks ...


0

It depends on the confidence of the issue reported by burp, when the confidence is certain, a complete payload for you to reproduce it is provided, usually a sleep command. If the confidence of burp is 'tentative' that usually means the original command and the same command with a ' return different responses, you can manually check what happens when you ...


Top 50 recent answers are included