Executive Summary

CVE-2025-9595 is a critical SQL injection vulnerability in the Student Information Management System 1.0, specifically in the /login.php file. The vulnerability occurs because the uname parameter is improperly handled and directly included in SQL queries without proper validation or sanitization. This allows attackers to inject malicious SQL code remotely, potentially manipulating database queries to gain unauthorized access or control. [1]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow attackers to gain unauthorized access to the database, extract sensitive information, modify or delete records, take full control of the system, and disrupt services. Exploiting this flaw requires no authentication, making it highly dangerous and capable of severely compromising system security and business continuity. [1]

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by testing the `uname` POST parameter in the `/login.php` file for SQL injection. Automated tools like sqlmap can be used to confirm the vulnerability by enumerating databases via the injection point. Example payloads to test include: `uname=111' RLIKE (SELECT (CASE WHEN (9713=9713) THEN 111 ELSE 0x28 END))-- MsHX` and `uname=111' AND (SELECT 3653 FROM (SELECT(SLEEP(5)))uJnN)-- uFsi`. Using sqlmap, a command might be: `sqlmap -u http://target/login.php --data "uname=111" --risk=3 --level=5` to detect SQL injection. [1]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2) Enforce strict input validation and filtering on the `uname` parameter to reject malicious payloads. 3) Minimize database user privileges by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. [1]

Useful 0 Not Useful 0