CVE-2025-10113
BaseFortify
Publication date: 2025-09-09
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_information_management_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-10113 is a critical SQL injection vulnerability in the itsourcecode Student Information Management System version 1.0, specifically in the file /admin/modules/room/index.php. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL queries. This can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, modification, or deletion of sensitive information. Attackers may gain full system control or disrupt services. Since it can be exploited remotely without authentication, it poses a significant risk to data confidentiality, integrity, and availability, potentially causing severe operational and security impacts. [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 'id' parameter in the /admin/modules/room/index.php file for SQL injection using techniques such as boolean-based blind, time-based blind, and UNION-based SQL injection. Example payloads include: - Boolean-based blind: view=edit&id=(SELECT (CASE WHEN (9931=9931) THEN 441 ELSE (SELECT 5045 UNION SELECT 1623) END)) - Time-based blind: view=edit&id=441 AND (SELECT 6978 FROM (SELECT(SLEEP(5)))SAYu) - UNION query: view=edit&id=441 UNION ALL SELECT NULL,NULL,CONCAT(0x71786b7671,0x564a4450615a56525766616a74726d58486b596b42776b5061594f474e6f69564c56665a6d666655,0x71706a7671),NULL,NULL,NULL,NULL,NULL-- - Additionally, the vulnerability was confirmed using the sqlmap tool, which can be used to automate detection. Vulnerable targets can also be identified using Google dorking with the query: inurl:admin/modules/room/index.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Use prepared statements with parameter binding to separate SQL code from user input. - Implement strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for routine operations. - Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known countermeasures have been documented. [1, 2, 3]