CVE-2025-15053
SQL Injection in code-projects SIS 1.0 /searchresults.php
Publication date: 2025-12-24
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian_ros | student_information_system | 1.0 |
| code-projects | student_information_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15053 is a critical SQL Injection vulnerability in the Student Information System version 1.0. It arises from improper input sanitization and the lack of parameterized queries, particularly in the /searchresults.php file's searchbox parameter. This flaw allows attackers to inject malicious SQL code remotely, enabling them to manipulate SQL queries. The vulnerability also affects other endpoints like /register.php and /index.php, allowing time-based blind SQL injection and authentication bypass. Exploits can extract sensitive data, bypass authentication, and manipulate database records. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database. They can exfiltrate sensitive data, bypass authentication mechanisms to gain unauthorized access, and manipulate or corrupt database records. This compromises the confidentiality, integrity, and availability of your system, potentially leading to data breaches, unauthorized access to user accounts, and disruption of services. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /searchresults.php endpoint with SQL injection payloads in the searchbox parameter. Example commands include using curl or similar tools to send payloads such as "a' and 1=1#" to check for SQL injection behavior. Additionally, time-based blind SQL injection can be tested on /register.php with payloads like "a' and sleep(3)#" to observe response delays. Boolean blind SQL injection and authentication bypass can be tested on /index.php login parameters with payloads like "username=yjh' and 1=1#" or "password=a' or 1=1#". Google dorking with queries like inurl:searchresults.php can help identify vulnerable targets. These methods help confirm the presence of SQL injection vulnerabilities. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries or prepared statements (e.g., using PHP PDO or MySQLi) to prevent direct concatenation of user inputs into SQL commands. Enforce strict input validation with whitelisting to reject SQL-specific characters in user inputs. Apply the Principle of Least Privilege by restricting database user permissions to only necessary tables and operations. If possible, replace the affected software with a non-vulnerable alternative. These measures aim to comprehensively eliminate the SQL Injection vulnerabilities. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to perform SQL Injection attacks that can lead to unauthorized access, data exfiltration, and manipulation of sensitive information. Such breaches can compromise the confidentiality and integrity of personal and sensitive data managed by the Student Information System. This exposure can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate strict controls to protect personal data and ensure its confidentiality and integrity. Therefore, exploitation of this vulnerability could lead to violations of these standards due to potential data breaches and unauthorized data access. [1, 2, 3]