dbcve.org
Hostel Management SystemApplication · Phpgurukul

CVE-2025-6155

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in PHPGurukul Hostel Management System 1.0. It has been classified as critical. Affected is an unknown function of the file /includes/login-hm.inc.php. The manipulation of the argument Username leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in PHPGurukul Hostel Management System 1.0 allows remote attackers to inject malicious SQL queries through the Username parameter in /includes/login-hm.inc.php. The lack of input sanitization enables attackers to manipulate SQL statements, potentially leading to unauthorized database access, authentication bypass, or data exfiltration.

MitigationImplement parameterized queries (prepared statements) for all database interactions, especially in the login function. Validate and sanitize all user inputs, and consider deploying a WAF as a temporary measure until the code is patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hostel Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if PHPGurukul Hostel Management System is installed
    Look for the application in your web root directory. Check for common paths like /hostel or /hostel-management-system, or search for files containing 'PHPGurukul' or 'Hostel Management System' in their content.
    Affected if The application is present on the server
  2. Verify the installed version
    Check for a version file, readme.txt, or any file containing version information within the application directory. The affected version is 1.0.
    Affected if The installed version is 1.0
  3. Locate the affected login file
    Navigate to the /includes/ directory within the application and confirm that login-hm.inc.php exists.
    Affected if The file /includes/login-hm.inc.php is present
  4. Inspect the login-hm.inc.php code for SQL injection vulnerability
    Open /includes/login-hm.inc.php and examine the SQL query handling the Username parameter. Look for direct concatenation of user input into SQL queries without prepared statements or parameter binding.
    Affected if The code contains unsanitized user input (Username parameter) being directly inserted into SQL queries
  5. Check if the login function processes user input
    Review how the Username parameter is handled when passed to the login function. Confirm whether any sanitization or parameterized queries are applied.
    Affected if User input is passed to SQL queries without sanitization or prepared statements

You are affected if PHPGurukul Hostel Management System version 1.0 is installed and the /includes/login-hm.inc.php file contains unsanitized user input in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database interactions, especially in the login function. Validate and sanitize all user inputs, and consider deploying a WAF as a temporary measure until the code is patched.

Recommended fix Moderate confidence
  1. Review the vulnerable file /includes/login-hm.inc.php and identify the SQL query that uses the Username parameter unsafely
  2. Replace the vulnerable SQL query with a prepared statement (parameterized query) using PDO or mysqli
  3. Ensure all user inputs are properly escaped or bound as parameters before being used in SQL queries
  4. Implement input validation to sanitize the Username field (e.g., length limits, allowed character patterns)
  5. Apply the principle of least privilege to the database user account used by the application
  6. If possible, disable the affected application until the code is remediated
  7. Consider deploying a WAF (Web Application Firewall) as an interim mitigation layer
Caveat This is a custom PHP application from PHPGurukul with no documented security update path; the vendor has not released a patched version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hostel Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6155 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data