githubEdit

Web Registration (Signup)

Registration mechanism might be vulnerable to compromise.

Register with the Same Username/Email Address as Existing User

We might be able to register the same username/email address as the existing user. It may affect the web server so be careful when testing. Here are examples of username to register.

admin
administrator
root

Alternatively, it’s worth to try various approach to register.

# Insert null byte
admin\0
admin%00

# Insert a space before username
 admin
%20admin

# Insert a space after username
admin 
admin%20

# Insert spaces around username
 admin 
%20admin%20

# Replace uppercase/lowercase
Admin
aDmIn

# Overflow (we need to find the longest characters that can be registered)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxadmin

Register Malicious Username/Email Address

XSS

We might be able to inject XSS in username when registration.

SSTI

It’s worth to try SSTI payloads if the website uses frameworks/template engines such as Flask Pug, Angular, etc. Register username with the following SSTI.

SQLi

If website queries the database items using username, we might be able to inject SQL command in the username. Register username with the following SQLi.

PHP Injection

CRLF (%0d%0a)

Inserting CRLF code (%0d%0a) after the username or email, it may cause unexpected behavior.

Broken Access Control

We might be able to break the access restrictions on target page by adding specific params when registration.

Last updated