dbcve.org
Hostel Management SystemApplication · Phpgurukul

CVE-2025-6154

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 and classified as critical. This issue affects some unknown processing of the file /includes/login.inc.php. The manipulation of the argument student_roll_no leads to sql injection. The attack may be initiated 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

A SQL injection vulnerability exists in PHPGurukul Hostel Management System 1.0 within the /includes/login.inc.php file. The student_roll_no parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands. This is a critical flaw as it can lead to unauthorized database access, data exfiltration, or potential system compromise.

MitigationImmediately implement prepared statements/parameterized queries for all database operations involving user input in the affected file. Additionally, apply input validation and output encoding. Until the fix is deployed, consider restricting network access to the application or disabling the affected login functionality.

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. Confirm PHPGurukul Hostel Management System installation
    Search for the application in your web root directory or check your deployed web applications for the presence of PHPGurukul Hostel Management System files.
    Affected if The application is present in your environment
  2. Verify the exact version number
    Check the application version by reviewing any version file, README, or about page within the Hostel Management System installation directory.
    Affected if The installed version is 1.0
  3. Locate the login.inc.php file
    Navigate to the /includes/ directory within the application root and confirm the existence of the login.inc.php file.
    Affected if The file /includes/login.inc.php exists in your installation
  4. Inspect the student_roll_no parameter handling
    Open /includes/login.inc.php and search for occurrences of 'student_roll_no' within SQL query strings. Examine whether this parameter is directly concatenated into queries without prepared statements, parameter binding, or escaping functions.
    Affected if The student_roll_no parameter is used in SQL queries without parameterized queries, prepared statements, or input sanitization
  5. Determine if the login functionality is accessible
    Verify that the login page using login.inc.php is accessible to users (check web server configuration and access controls).
    Affected if The login functionality is active and accessible to potential attackers

Your environment is affected if you are running PHPGurukul Hostel Management System version 1.0 with the /includes/login.inc.php file containing unsanitized SQL queries using the student_roll_no parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately implement prepared statements/parameterized queries for all database operations involving user input in the affected file. Additionally, apply input validation and output encoding. Until the fix is deployed, consider restricting network access to the application or disabling the affected login functionality.

Fix this in Hostel Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6154 — 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-6154 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