CVE-2025-10811
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-22

Last updated on: 2026-04-29

Assigner: VulDB

Description
A flaw has been found in code-projects Hostel Management System 1.0. This affects an unknown function of the file /justines/admin/mod_comments/index.php?view=view. Executing manipulation of the argument ID can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-22
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-09-22
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
angeljudesuarez hostel_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-10811 is a critical SQL injection vulnerability in the Hostel Management System version 1.0, specifically in the file /justines/admin/mod_comments/index.php when handling the 'view=view' parameter with the 'ID' argument. The vulnerability occurs because the application does not properly validate or sanitize the 'ID' parameter, allowing attackers to inject malicious SQL code into database queries. This can be exploited remotely without authentication, enabling attackers to manipulate SQL queries to access, modify, or delete sensitive data in the backend database. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized access to the backend database, allowing attackers to read, modify, or delete sensitive data, thereby compromising data confidentiality, integrity, and availability. It can also result in full system control, data leakage, data tampering, and potential service disruption. Since exploitation requires no authentication and is easy to perform, it poses a severe threat to system security and business continuity. [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 vulnerable parameter 'id' in the URL '/justines/admin/mod_comments/index.php?view=view&id=4' for SQL injection. Common detection methods include using SQL injection payloads such as boolean-based blind SQL injection (e.g., id=4' AND 1=1 -- ), error-based SQL injection, time-based blind SQL injection (e.g., using SLEEP() function), or UNION-based SQL injection. Automated tools like sqlmap can be used to confirm the vulnerability and extract data. Example command using sqlmap: sqlmap -u "http://target/justines/admin/mod_comments/index.php?view=view&id=4" --batch --dbs [2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing prepared statements with parameterized queries to separate SQL code from user input, enforcing strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. Additionally, conducting regular security audits to detect and address vulnerabilities promptly is recommended. If possible, replacing the affected component or product with a secure alternative is advised since no known mitigations currently exist. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart