CVE-2025-10813
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-10813 is a critical SQL injection vulnerability in the Hostel Management System version 1.0, specifically in the file /justines/admin/mod_reports/index.php. The vulnerability arises because the application improperly handles the 'start' or 'Home' parameter, failing to validate or sanitize user input before using it in SQL queries. This allows remote attackers to inject malicious SQL code, potentially executing arbitrary SQL commands without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve, modify, or delete sensitive data. It can also enable full system control and cause service disruption. Since no authentication is required, attackers can remotely exploit this flaw to compromise the confidentiality, integrity, and availability of the system. [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 'start' parameter in POST requests to the file /justines/admin/mod_reports/index.php for SQL injection. Automated tools like sqlmap can be used to confirm the vulnerability by attempting SQL injection on this parameter. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:justines/admin/mod_reports/index.php. Example command using sqlmap: sqlmap -u "http://target/justines/admin/mod_reports/index.php" --data="start=1" --risk=3 --level=5 --batch [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'start' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding high-privilege accounts like 'root' or 'admin' for routine database operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3]