CVE-2025-10812
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-10812 is a critical SQL injection vulnerability in the Hostel Management System version 1.0, specifically in the file /justines/admin/mod_amenities/index.php via the 'id' parameter. Due to insufficient input validation, attackers can inject malicious SQL code remotely without authentication. This allows unauthorized manipulation of SQL queries, potentially leading to unauthorized database access, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely access and manipulate the database without authentication. They can read, modify, or delete sensitive data, potentially disrupt services, and gain full system control. This compromises the confidentiality, integrity, and availability of the system and its data. [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 URL '/justines/admin/mod_amenities/index.php?view=view' for SQL injection. Commands using sqlmap can be used to automate detection, for example: sqlmap -u "http://target/justines/admin/mod_amenities/index.php?view=view&id=1" --batch. Manual testing can include injecting payloads such as 'AND 1=1' or 'AND 1=2' to observe differences in responses, or using time-based payloads like 'SLEEP(5)' to detect delays indicating SQL injection. Examples include: - Boolean-based test: curl "http://target/justines/admin/mod_amenities/index.php?view=view&id=8 AND 3354=3354" - Time-based test: curl "http://target/justines/admin/mod_amenities/index.php?view=view&id=8 AND SLEEP(5)" These tests help confirm if the 'id' parameter is vulnerable to SQL injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameterized queries to prevent SQL injection. - Apply strict input validation and filtering on the 'id' parameter to ensure it only accepts expected formats (e.g., numeric values). - Avoid using high-privilege database accounts (such as root or admin) for the application database connection; use least privilege principles. - Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. - If possible, replace the affected component with a secure alternative. These steps help protect system security and data integrity against exploitation of this vulnerability. [2, 3]