CVE-2026-10877
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 security vulnerability has been detected in SourceCodester Ship Ferry Ticket Reservation System up to 1.0. This impacts an unknown function of the file /admin/login.php of the component Admin Login. Such manipulation of the argument Username leads to sql injection. The attack can be executed remotely. The exploit has been disclosed publicly 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 · moderate confidenceSQL injection vulnerability in SourceCodester Ship Ferry Ticket Reservation System (up to v1.0) in the admin login form at /admin/login.php. The Username parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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 application installationSearch for the file /admin/login.php in your web server's document root. Common paths include /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\ depending on your server OS.Affected if The file /admin/login.php exists and belongs to SourceCodester Ship Ferry Ticket Reservation System
-
Confirm the application versionCheck for a version identifier in the source code (e.g., in header.php, footer.php, or config files). Look for comments like 'version 1.0' or similar.Affected if The installed version is 1.0 or cannot be determined (assume affected)
-
Examine the login.php SQL queryOpen /admin/login.php and locate the SQL query that handles the Username parameter. Look for code that directly concatenates the username input into the query string without using prepared statements or escaping functions.Affected if The code contains a query like 'SELECT * FROM users WHERE username = '" . $_POST['username'] . "' (or similar string concatenation) without parameterized queries
-
Verify the admin login endpoint is accessibleAttempt to access the login page via HTTP/HTTPS at /admin/login.php. Confirm the page loads and accepts POST requests for username/password.Affected if The admin login page is accessible and the vulnerable code is in use
-
Check for input sanitization on Username fieldReview the login.php code for any sanitization applied to the username POST parameter before using it in the SQL query. Look for functions like mysqli_real_escape_string, htmlspecialchars, or parameter binding.Affected if No sanitization function is applied to the username parameter before it is used in the SQL query
Your environment is affected if you have the Ship Ferry Ticket Reservation System installed, the admin/login.php file exists, and the code uses unsanitized dynamic SQL with the username parameter in the login query.
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 the current SQL query logic in /admin/login.php with parameterized queries (prepared statements) to properly sanitize user input. Implement input validation as an additional defense layer.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10877 — 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-10877 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