Log in to the target site, go to the authentication page, and check if it uses multiple types of authentication, such as password, email, Google, and Facebook
2
Enter the request using an incorrect password and email address. Intercept the POST request using Bupr Suite
3
Then examine the intercepted request and see if you see a parameter called auth_type
4
If you see such a parameter that specifies the type of authentication with Google or Facebook or password and email, send the request to the repeater
5
And then change the authentication type in the auth_type parameter to facebook
"auth_type": "email" → "facebook"
6
If the user information is displayed in the server response, the authentication bypass is confirmed
Email Domain Validation Bypass
1
Access registration form
2
Enter email test@redacted.com, Capture POST request in Burp
3
Notice server prepends or validates only suffix (@redacted.com)
email=bishal@redacted.com
4
Modify email domain to any external domain
email=bishal0x01@bugcrowdninja.com
5
Send request
6
Receive verification email at bishal0x01@bugcrowdninja.com
7
Click link, Account activated
Change The Letter Case
1
Use the enumerate Application command to perform the identification process and obtain the sensitive paths of the admin panel
2
Access known admin path
GET /admin HTTP/1.1
3
If it gives you a 403 error with a 401 in response, then send the following request
Navigate to the SignUp page of the target website, typically located at a URL like /signup or /register Open https://example.com/signup in the browser
2
Identify the “Full Name” input field in the SignUp form, which is prone to processing user input directly into database queries Find the text box labeled “Full Name” in the form
3
Enter the payload ' OR 1=1 -- into the Full Name field to attempt bypassing the query’s conditions and access unauthorized data Input John' OR 1=1 -- in the Full Name field
4
Click the “Sign Up” button to send the payload to the server via a POST request
5
Look for a generic error (“Invalid input”) or a 400/500 status code, indicating the payload was blocked, or unexpected success, suggesting a vulnerability
6
If a 400/500 error appears, modify the payload to ' OR 1=2 -- and submit again. Compare responses: if ' OR 1=1 -- allows form submission or data access (account creation without valid input) while ' OR 1=2 -- fails, it confirms SQL injection, as the true condition (1=1) altered the query’s logic
White Box
Bypass Authentication via Path Traversal
1
Map the entire target system using Burp Suite
2
Draw all endpoints in XMind
3
Decompile the web server based on the programming language used
4
In the code, look for classes and functions that process authentication endpoints
5
Then, in the class that handles the authentication endpoint, look for paths in the code where exceptions exist and authentication is bypassed, like in the code below
VSCode (Regex Detection)
RipGrep (Regex Detection (Linux))
Vulnerable Code Patterns
6
Also review how the request is received and processed
7
The final request will look like the following
Authentication Bypass via Error Dispatcher
1
Map the entire target system using the Burp Suite tool
2
Map the entry points and endpoints in Xmind
3
Decompile the application based on the programming language used
4
Note all pre-login endpoints and license-related endpoints in the code and configuration that make security decisions based on the URL path, such as the path below
5
Intentionally add invalid paths to the URL and send requests to trigger error handling
6
Then review this path in the code under the error-handling logic to check whether an unauthenticated user is given a session for communication or not
VSCode (Regex Detection)
RipGrep (Regex Detection (Linux))
Vulnerable Code Patterns
7
Finally, by abusing the path error, it is possible to obtain a session for connection and interaction