CVE-2026-14688
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 itsourcecode Online Hotel Management System 1.0. The affected element is an unknown function of the file /admin/login.php. The manipulation of the argument email leads to sql injection. The attack may 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 confidenceSQL injection vulnerability in itsourcecode Online Hotel Management System 1.0's /admin/login.php file. The email parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through the login form.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify the installed applicationLocate itsourcecode Online Hotel Management System in the web root directory. Check for application files and any version indicators (readme, changelog, or version comments in source files).Affected if The application is itsourcecode Online Hotel Management System version 1.0 or if the version cannot be determined but the product is present.
-
Verify the affected file existsCheck if the file /admin/login.php exists in the web application directory. This is the specific file containing the vulnerable code.Affected if The file /admin/login.php exists in the deployed application.
-
Confirm the application is accessibleVerify that the login page at /admin/login.php is accessible over HTTP/HTTPS from the network.Affected if The login page is reachable and accepts requests on the email parameter.
-
Inspect the login.php source codeOpen /admin/login.php in a text editor or use 'grep' to search for the email parameter handling. Look for SQL query construction involving the email variable without prepared statements or parameter binding.Affected if The code contains direct SQL query concatenation using the email parameter without sanitization, prepared statements, or parameterized queries.
-
Compare installed version to affected rangeIf a version file or identifier is found, compare it to version 1.0. If no version is found, treat as potentially affected.Affected if The installed version is 1.0 or cannot be determined (unknown version).
The environment is affected if itsourcecode Online Hotel Management System 1.0 is deployed and the /admin/login.php file contains unsanitized SQL query handling for the email 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 dynamic SQL queries with parameterized queries/prepared statements for the email parameter in login.php, and implement proper input validation and escaping.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14688 — 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-2026-14688 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