dbcve.org
Hotel And Lodge Management SystemApplication · Nikhil Bhalerao

CVE-2025-11403

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 vulnerability was found in SourceCodester Hotel and Lodge Management System 1.0. Affected by this issue is some unknown functionality of the file /del_booking.php. Performing manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit has been made public and could 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 SourceCodester Hotel and Lodge Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter in /del_booking.php. The lack of input sanitization or parameterized queries enables complete database compromise.

MitigationReplace dynamic SQL queries with parameterized statements/prepared queries, implement strict input validation on the ID parameter, and apply principle of least privilege to database credentials.

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. Identify if Hotel and Lodge Management System is present
    Locate the web application directory and check for typical files like index.php, or search for the string 'Hotel And Lodge Management System' in source files
    Affected if The application is installed on the server
  2. Verify the installed version is 1.0
    Check for a version file, about page, or look for version strings in PHP source files (search for 'version' or '1.0' in code)
    Affected if Installed version equals 1.0
  3. Confirm del_booking.php exists and is accessible
    Check for the file at the expected path (commonly /del_booking.php or within an admin/booking subdirectory) in the web root
    Affected if The del_booking.php file exists and is web-accessible
  4. Inspect the ID parameter handling in del_booking.php
    Open del_booking.php and locate the SQL query that uses the ID parameter - examine whether it uses prepared statements/parameterized queries or direct string concatenation
    Affected if The code constructs SQL queries by directly inserting the ID parameter without using prepared statements or input sanitization
  5. Test the ID parameter for SQL injection vulnerability
    Send a crafted request to del_booking.php with a test payload in the ID parameter (e.g., ID=1' OR '1'='1) and observe if the application returns database errors or unexpected results
    Affected if The application reflects SQL syntax errors or behaves differently based on the injected payload, indicating the parameter is not properly sanitized

You are affected if the Hotel and Lodge Management System version 1.0 is installed with a web-accessible del_booking.php file that uses unparameterized SQL queries with the ID 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.

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

Replace dynamic SQL queries with parameterized statements/prepared queries, implement strict input validation on the ID parameter, and apply principle of least privilege to database credentials.

Recommended fix Moderate confidence
  1. Block or restrict external access to /del_booking.php via web server configuration (e.g., .htaccess, NGINX location deny) or rename the file to prevent direct requests.
  2. If the booking deletion feature is not required, delete the del_booking.php file entirely.
  3. Modify del_booking.php to use parameterized queries (PDO/MySQLi) and ensure the ID parameter is cast to an integer or validated before being used in the SQL statement.
  4. Add proper authentication and authorization checks to verify the user is allowed to delete bookings before performing the operation.
  5. Deploy a Web Application Firewall (WAF) rule to detect and block SQL injection attempts targeting the ID parameter.
  6. Monitor access and error logs for any suspicious requests to del_booking.php and investigate promptly.
  7. When a patched release becomes available, upgrade the software to incorporate the vendor fix.
Caveat Disabling or removing del_booking.php will prevent booking deletion until the functionality is re-implemented securely.

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
  • Implementation3.0 h
  • Testing5.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,250
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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