dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10185

HIGH · 7.3 CVSS v3.1 Published 2026-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A weakness has been identified in SourceCodester Hospitals Patient Records Management System 1.0. Affected is an unknown function of the file /classes/Users.php?f=save. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.

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 confidence

SQL injection vulnerability in SourceCodester Hospitals Patient Records Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in the /classes/Users.php?f=save endpoint. The lack of proper input sanitization or parameterized queries in the save function enables attackers to manipulate database queries, potentially exposing or modifying sensitive patient records.

MitigationImplement prepared statements/parameterized queries for all database operations in the affected save function, and apply strict input validation on the ID parameter before using it in SQL queries. Conduct a full code audit of the application to identify and remediate similar SQL injection vulnerabilities.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the application identity
    Inspect the application files or HTTP headers to verify the system is SourceCodester Hospitals Patient Records Management System. Look for application banners, readme files, or page footers that identify the software name.
    Affected if The application is not SourceCodester Hospitals Patient Records Management System
  2. Verify the software version
    Check the application's version number, typically found in a version file, about page, or in the source code comments. Compare against version 1.0.
    Affected if The installed version is not 1.0 (if version differs, still examine the code for similar patterns)
  3. Locate the vulnerable file
    Navigate to the /classes/Users.php file in the web root directory and confirm its existence. Open the file to examine the save function.
    Affected if The file /classes/Users.php does not exist or does not contain a save function
  4. Identify vulnerable code patterns
    Within /classes/Users.php, locate the save function. Search for SQL query execution where the ID parameter is used directly in the query string without parameter binding, prepared statements, or escaping functions.
    Affected if The ID parameter is concatenated directly into SQL queries without sanitization or prepared statements
  5. Confirm user input handling
    Trace how the ID parameter reaches the save function from the HTTP request. Verify that user-supplied input flows through to the SQL query without validation.
    Affected if User-controlled input from the ID parameter reaches the SQL query unsanitized

If the system runs SourceCodester Hospitals Patient Records Management System version 1.0 and the ID parameter in /classes/Users.php?f=save is used without parameterized queries or input sanitization, the environment is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations in the affected save function, and apply strict input validation on the ID parameter before using it in SQL queries. Conduct a full code audit of the application to identify and remediate similar SQL injection vulnerabilities.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10185 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10185 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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