CVE-2025-10796
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-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?
CVE-2025-10796 is a critical SQL injection vulnerability in the Hostel Management System 1.0, specifically in the file /justines/admin/login.php. The vulnerability occurs because the application directly uses the 'email' parameter from POST requests in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data tampering, full system control, and service disruption. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, tampering with data, gaining full control over the system, and causing service disruptions. Since it requires no authentication to exploit, attackers can remotely launch attacks using various SQL injection techniques, potentially compromising the entire system and business continuity. [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 vulnerable parameter 'email' in the /justines/admin/login.php endpoint for SQL injection using various techniques such as boolean-based blind, error-based, and time-based blind injections. Example payloads include: - Boolean-based blind: email=admin' RLIKE (SELECT (CASE WHEN (3387=3387) THEN 0x61646d696e ELSE 0x28 END))-- - Error-based: email=admin' OR (SELECT 7308 FROM(SELECT COUNT(*),CONCAT(0x71717a7a71,(SELECT (ELT(7308=7308,1))),0x7171717071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - Time-based blind: email=admin' AND (SELECT 8682 FROM (SELECT(SLEEP(5)))cUSM)-- Additionally, the sqlmap tool can be used to automate detection and exploitation of this SQL injection vulnerability. [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 high-privilege accounts for routine operations. - Conduct regular security audits to detect and fix vulnerabilities promptly. [1]