CVE-2025-6153
BaseFortify
Publication date: 2025-06-17
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 |
|---|---|---|
| phpgurukul | 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-6153 is a critical SQL injection vulnerability in PHPGurukul Hostel Management System 1.0, specifically in the /admin/students.php file. The vulnerability arises because the search_box parameter is used directly 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, modification, deletion, or full system compromise. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data modification or deletion, full system compromise, and potential disruption of services. Attackers can exploit the SQL injection remotely without needing authentication, which increases the risk of widespread damage and loss of data integrity and availability. [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 `search_box` parameter in the `/admin/students.php` file for SQL injection flaws. Tools like sqlmap can be used to automate detection. Example command using sqlmap: sqlmap -u "http://target/admin/students.php" --data="search_box=example" --risk=3 --level=5 --batch. Additionally, manual testing with payloads such as boolean-based blind injection (using EXTRACTVALUE), error-based injection (using FLOOR or RAND), time-based injection (using SLEEP), and UNION-based injection can help identify the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input. 2) Apply strict input validation and filtering on the `search_box` parameter to ensure inputs conform to expected formats. 3) Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations. 4) Conduct regular security audits to identify and fix vulnerabilities promptly. [1]