CVE-2025-15168
SQL Injection in itsourcecode Student Management System /statistical.php
Publication date: 2025-12-29
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 |
|---|---|---|
| itsourcecode | student_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the itsourcecode Student Management System 1.0, specifically in an unknown function within the /statistical.php file. By manipulating the argument ID, an attacker can inject malicious SQL code. The attack can be performed remotely, and an exploit is publicly available.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or data deletion. Since the attack can be executed remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access to and manipulation of sensitive data through SQL injection, which can lead to data leakage and tampering. Such unauthorized data exposure and integrity violations can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information. Therefore, exploitation of this vulnerability could compromise compliance with these standards by exposing or altering protected data without authorization. [1, 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 'id' parameter in the /statistical.php file for SQL injection. One suggested command to confirm the vulnerability is using sqlmap: `python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/statistical.php?id=1" --dbms=mysql --current-db`. Additionally, Google Dorking can be used to identify vulnerable targets with the query: `inurl:statistical.php`. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements and parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering, such as numeric validation for the 'id' parameter. 3) Minimize database user permissions to avoid using high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with an alternative solution. [1, 3]