CVE-2025-11405
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 was identified in SourceCodester Hotel and Lodge Management System 1.0. This vulnerability affects unknown code of the file /del_tax.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit is publicly available and might 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 confidenceA SQL injection vulnerability exists in the del_tax.php file of SourceCodester Hotel and Lodge Management System 1.0 where the ID parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code and potentially exfiltrate or modify database contents.
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 installed product and versionLocate the Hotel and Lodge Management System installation directory and check for version identifiers such as a version.php file, README, or admin panel version display. Compare the found version to 1.0.Affected if The installed version is Hotel and Lodge Management System 1.0.
-
Locate vulnerable fileSearch the web root directory for the file del_tax.php. Common paths may include /admin/, /php/, or the main application directory.Affected if The file del_tax.php exists in the application directory.
-
Inspect del_tax.php for unsafe SQL usageOpen del_tax.php in a text editor and examine the code around line where the ID parameter is retrieved (e.g., $_GET['id'] or $_POST['id']) and used directly in SQL queries without prepared statements, parameter binding, or sanitization functions.Affected if The ID parameter is concatenated directly into SQL queries without input validation or parameterized queries.
-
Verify application is accessible over networkAttempt to access del_tax.php via HTTP/HTTPS from a remote host using curl or a browser, e.g., GET /del_tax.php?id=1Affected if The del_tax.php file is accessible via web requests and accepts the ID parameter.
-
Check database user privilegesIf database access is available, examine the database user configured in the application's connection settings (often in config.php or db.php) to determine if it has elevated privileges that could be exploited.Affected if The application database user has permissions beyond what the application requires, allowing potential data exfiltration or modification.
A user is affected if they are running Hotel and Lodge Management System version 1.0 with the del_tax.php file accessible via web and containing direct SQL concatenation with the ID parameter.
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 direct string concatenation in SQL queries with parameterized queries (prepared statements) and implement proper input validation on the ID parameter to prevent SQL injection attacks.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11405 — 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-11405 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