CVE-2025-6155
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-6155 is a critical SQL injection vulnerability in the PHPGurukul Hostel Management System 1.0, specifically in the /includes/login-hm.inc.php file. The vulnerability occurs because the application does not properly validate or sanitize the 'username' parameter before using it in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating database queries to access, modify, or delete sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, and potential full control over the affected system. It can also disrupt services by compromising the integrity and availability of the application. Since the attack can be launched remotely without authentication, it poses a significant risk to the security and continuity 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 'username' parameter in the /includes/login-hm.inc.php file for SQL injection. One method is to use a time-based blind SQL injection payload, such as: username=codeprojects' AND (SELECT 7877 FROM (SELECT(SLEEP(5)))KFQM)-- ZfDJ&pwd=password&login-submit=, which causes a delay in the database response if vulnerable. Additionally, tools like sqlmap can be used to automate detection against the affected endpoint. Vulnerable targets can also be identified using Google dorking with the query: inurl:includes/login-hm.inc.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on user inputs such as the 'username' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Regular security audits should also be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended. [2, 3, 1]