CVE-2026-10288
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 code-projects Hotel and Tourism Reservation System 1.0. This issue affects the function password_verify of the file /admin/login.php of the component Admin Login. Such manipulation of the argument Password leads to improper authentication. It is possible to launch the attack 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 · moderate confidenceThe admin login in Hotel and Tourism Reservation System 1.0 (/admin/login.php) contains an improper authentication vulnerability in the password_verify function. Manipulation of the Password argument allows attackers to bypass authentication and gain unauthorized admin access. The exploit is publicly available, indicating ease of exploitation.
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.
-
Locate the Hotel and Tourism Reservation System installationSearch for the presence of the application by looking for known file paths such as /admin/login.php, /login.php, or the main index file. Check your web server document root for directories containing 'hotel', 'reservation', or 'tourism' in their names.Affected if The application directory structure with admin/login.php exists on the server.
-
Verify the vulnerable admin login page existsCheck if the file /admin/login.php exists in your web server's accessible paths. This is the specific endpoint mentioned in the CVE as having the authentication flaw.Affected if The file /admin/login.php is present and accessible via HTTP/HTTPS.
-
Inspect the authentication logic in login.phpOpen /admin/login.php and locate the password verification logic. Look for usage of the password_verify function that may be accepting manipulated arguments or using insecure comparison methods (such as loose comparison == instead of ===, or passing user-controlled input directly).Affected if The login.php contains password_verify logic that can be bypassed through argument manipulation or insecure comparison.
-
Confirm admin panel accessibilityAttempt to access the admin panel directory or check if /admin/ is accessible without authentication. Verify that unauthenticated users can reach admin functions after bypassing login.Affected if The admin panel is reachable and the authentication bypass allows full admin access.
If the Hotel and Tourism Reservation System 1.0 is installed with the vulnerable /admin/login.php file containing the manipifiable password verification logic, the environment is affected by this CVE.
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 dataFix the password_verify implementation to use proper PHP password verification (password_verify() with correctly hashed passwords from the database). Validate that the authentication logic correctly compares the submitted password against the stored hash using secure comparison functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10288 — 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-10288 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