CVE-2026-10186
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 code-projects Online Hospital Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /patient.php. Such manipulation of the argument editid 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 · high confidenceSQL injection vulnerability in the /patient.php file of code-projects Online Hospital Management System 1.0. The editid parameter is not properly sanitized, allowing attackers to inject malicious SQL queries remotely.
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.
-
Confirm the application installationCheck if the Online Hospital Management System from code-projects is installed. Look for the application in your web root directory and verify the presence of patient.php file.Affected if The system is running code-projects Online Hospital Management System version 1.0 with patient.php present
-
Locate the vulnerable patient.php fileSearch for the patient.php file in your web application directory structure. This file is typically located in the main application root or admin directory.Affected if The patient.php file exists in the application
-
Verify the editid parameter is accessibleCheck if patient.php accepts the 'editid' parameter via GET or POST requests. Review the application routes or test accessing patient.php?editid=1 to confirm the parameter is processed.Affected if The editid parameter is accepted and processed by patient.php without proper sanitization
-
Review database query implementation in patient.phpExamine the source code of patient.php to verify if the editid parameter is used directly in SQL queries without prepared statements, parameterized queries, or input sanitization functions.Affected if The editid parameter is directly concatenated into SQL queries without sanitization or parameterization
-
Confirm database user privilegesReview the database configuration to understand what privileges the application database user has. SQL injection impact depends on the permissions granted to the application database user.Affected if The database user has elevated privileges (such as SELECT, INSERT, UPDATE, DELETE on multiple tables)
Your environment is affected if you are running code-projects Online Hospital Management System version 1.0 and the patient.php file exists with the editid parameter being used in unsanitized SQL queries.
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 statements/prepared statements and implement proper input validation on the editid parameter. Conduct a full codebase audit for similar SQL injection vulnerabilities.
- 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-10186 — 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-10186 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