CVE-2025-10797
BaseFortify
Publication date: 2025-09-22
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 |
|---|---|---|
| angeljudesuarez | hostel_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-10797 is a critical SQL injection vulnerability in the Hostel Management System 1.0, specifically in the '/justines/index.php' file. It occurs because the 'log_email' parameter is improperly handled and used directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, potentially gaining unauthorized access to the database, leaking or tampering data, taking full control of the system, and disrupting services. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can exploit it remotely without any authentication, which can lead to loss of sensitive information, damage to system integrity, and interruption of business operations. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'log_email' parameter in the '/justines/index.php' file for SQL injection using various techniques such as boolean-based blind, error-based, and time-based blind injections. Example payloads include: - Boolean-based blind: log_email=admin@123' RLIKE (SELECT (CASE WHEN (8714=8714) THEN 0x61646d696e40313233 ELSE 0x28 END))-- - Error-based: log_email=admin@123' OR (SELECT 5038 FROM(SELECT COUNT(*),CONCAT(0x716b786271,(SELECT (ELT(5038=5038,1))),0x71717a7a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - Time-based blind: log_email=admin@123' AND (SELECT 9523 FROM (SELECT(SLEEP(5)))ADRw)-- Additionally, the vulnerability was confirmed using the sqlmap tool, which can be used to automate detection. [1]
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 like 'root' or 'admin' for routine operations. - Conduct regular security audits to detect and fix vulnerabilities promptly. [1]