CVE-2025-11402
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 · uneditedA vulnerability has been found in SourceCodester Hotel and Lodge Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /del_curr.php. Such manipulation of the argument ID leads to sql injection. The attack may be performed from remote. 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 confidenceSQL injection vulnerability in SourceCodester Hotel and Lodge Management System 1.0 where the ID parameter in /del_curr.php is not properly sanitized before being used in SQL queries. An attacker can inject malicious SQL statements to manipulate database queries, potentially extracting, modifying, or deleting sensitive data. The vulnerability is remotely exploitable and a public exploit exists.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm application installation and versionLocate the Hotel and Lodge Management System installation. Check version information typically found in about page, header files, or version configuration. The affected version is exactly 1.0.Affected if The installed version is 1.0 of Nikhil Bhalerao Hotel And Lodge Management System
-
Locate the vulnerable file del_curr.phpSearch for del_curr.php in the web root or application directory. This file handles deletion operations in the system.Affected if The file del_curr.php exists in the application structure
-
Inspect ID parameter handling in del_curr.phpOpen del_curr.php and examine how the ID parameter is received and processed. Look for $_GET or $_POST usage of 'ID' parameter without sanitization.Affected if The ID parameter is used directly in SQL queries without sanitization or prepared statements
-
Verify lack of prepared statementsReview the PHP code in del_curr.php to confirm whether database queries use prepared statements or parameterized queries, or if they concatenate user input directly into SQL strings.Affected if SQL queries in del_curr.php do not use prepared statements and directly incorporate the ID parameter
-
Confirm network accessibilityVerify that del_curr.php is accessible over the network. Since the vulnerability is remotely exploitable, the file must be reachable via HTTP/HTTPS requests.Affected if The del_curr.php endpoint is accessible from the network without authentication restrictions
The system is vulnerable if it runs version 1.0 of the Hotel and Lodge Management System with the del_curr.php file accessible and the ID parameter processed without prepared statements.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) in del_curr.php to prevent SQL injection. Alternatively, implement proper input validation and escaping for the ID parameter. Apply the fix immediately given the critical CVSS score and public exploit availability.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11402 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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