dbcve.org
Hotel And Lodge Management SystemApplication · Nikhil Bhalerao

CVE-2025-11397

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-07
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 security flaw has been discovered in SourceCodester Hotel and Lodge Management System 1.0. The affected element is an unknown function of the file /login.php. Performing manipulation of the argument email results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may be exploited.

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 · moderate confidence

SQL injection vulnerability in SourceCodester Hotel and Lodge Management System 1.0 allows remote attackers to inject arbitrary SQL commands via the email parameter in /login.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries without authentication.

MitigationReplace dynamic SQL queries in login.php with prepared statements/parameterized queries for the email parameter, and validate all user inputs before database interaction.

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
Hotel And Lodge 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 the installed product and version
    Identify if the system is running SourceCodester Hotel and Lodge Management System version 1.0 (also known as Nikhil Bhalerao Hotel And Lodge Management System 1.0). Check application metadata, about page, or version file if available.
    Affected if The system is running Hotel and Lodge Management System version 1.0
  2. Locate the login.php file
    Find the login.php file in the web application's root directory. This file is typically in the public HTML directory or application root.
    Affected if The login.php file exists in the application directory
  3. Inspect email parameter handling in login.php
    Examine the source code of login.php and look for how the email POST or GET parameter is used in SQL queries. Check if the query uses prepared statements with placeholders like ? or named parameters, or if it directly concatenates the email variable into the SQL string.
    Affected if The email parameter is directly concatenated into SQL queries without using parameterized queries or input sanitization functions
  4. Check database query implementation
    Review the database query code in login.php that handles the login functionality. Look for functions like mysqli_prepare, PDO::prepare, or similar parameterized query methods. If you see string concatenation or interpolation like SELECT * FROM users WHERE email = '$email', the vulnerability exists.
    Affected if SQL queries in login.php use string concatenation or interpolation for the email parameter instead of prepared statements

If the system runs Hotel and Lodge Management System 1.0 and login.php contains SQL queries that directly use the email parameter without parameterized queries, the system is affected by CVE-2025-11397.

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

Replace dynamic SQL queries in login.php with prepared statements/parameterized queries for the email parameter, and validate all user inputs before database interaction.

Recommended fix Moderate confidence
  1. 1. Review the /login.php file and identify the vulnerable SQL query using the 'email' parameter without proper input sanitization or parameterized queries.
  2. 2. Replace string concatenation in SQL queries with prepared statements (PDO or MySQLi with parameter binding).
  3. 3. Apply input validation: sanitize the email parameter using filter_var() and regex to ensure proper email format before using in queries.
  4. 4. Implement least-privilege database user account for the application that only has necessary permissions.
  5. 5. Add Web Application Firewall (WAF) rules to detect and block SQL injection attempts as an interim protective measure.
  6. 6. Consider implementing additional authentication mechanisms (e.g., multi-factor authentication) to reduce impact of potential credential theft.
Caveat No official patch or newer version available from vendor; manual code remediation required

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

Fix this in Hotel And Lodge Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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