dbcve.org
Hotel And Lodge Management SystemApplication · Nikhil Bhalerao

CVE-2025-11404

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 determined in SourceCodester Hotel and Lodge Management System 1.0. This affects an unknown part of the file /pages/save_tax.php. Executing manipulation of the argument percentage can lead to sql injection. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized.

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's /pages/save_tax.php allows remote attackers to inject malicious SQL queries via the 'percentage' parameter. With a CVSS score of 9.8, this critical flaw could enable complete database compromise, including unauthorized data access, modification, or potential remote code execution depending on database configuration.

MitigationImplement parameterized queries (prepared statements) for all database operations involving the percentage parameter, apply strict input validation, and ensure the database user follows least-privilege principles. Review and audit other files in the application for similar SQL injection vulnerabilities.

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 the Hotel and Lodge Management System is installed
    Look for the application directory on the web server. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\. Search for files containing 'hotel', 'lodge', or 'management' in the name.
    Affected if The application is found and served by the web server
  2. Check the installed version
    Check application version information - look for a version file, about page, or check the source code for version identifiers. The affected version is specifically 1.0.
    Affected if The installed version is exactly 1.0
  3. Verify the vulnerable file exists
    Check if the file /pages/save_tax.php exists in the web application directory. This is the file containing the SQL injection vulnerability.
    Affected if The file pages/save_tax.php exists in the application
  4. Confirm the application is network-accessible
    Determine if the web application is accessible over the network. Attempt to access the login page or any public-facing endpoint.
    Affected if The application is accessible from a network or the internet
  5. Check if the save_tax.php endpoint accepts input
    Examine the application's tax management functionality. The save_tax.php endpoint receives a 'percentage' parameter. Look for tax configuration or creation features in the application.
    Affected if The tax functionality that uses save_tax.php is accessible and accepts user input

A user is affected if they are running version 1.0 of the Hotel and Lodge Management System with the pages/save_tax.php file present and accessible, where the tax percentage input feature is enabled.

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 operations involving the percentage parameter, apply strict input validation, and ensure the database user follows least-privilege principles. Review and audit other files in the application for similar SQL injection vulnerabilities.

Recommended fix Moderate confidence
  1. Locate the vulnerable file /pages/save_tax.php in the application root.
  2. Open the file in a text editor and locate the SQL query that uses the 'percentage' parameter (e.g., $_POST['percentage'] or $_GET['percentage']).
  3. Replace the direct concatenation of the parameter into the SQL string with a prepared statement (using PDO or MySQLi).
  4. Bind the 'percentage' value as an integer or float, for example: $stmt->bindValue(':percentage', (int)$percentage, PDO::PARAM_INT);
  5. Alternatively, cast the input to an integer or float before using it: $percentage = (int)$_POST['percentage']; or $percentage = (float)$_POST['percentage'];
  6. Ensure the database user credentials used by the application have only the minimum required privileges (e.g., no DROP, CREATE, or GRANT).
  7. Test the changes in a staging environment by submitting valid tax percentage values and confirming correct storage in the database.
  8. Deploy the patched file to production.

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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