dbcve.org
Hospital Management SystemApplication · Fabian

CVE-2024-10170

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 vulnerability, which was classified as critical, has been found in code-projects Hospital Management System 1.0. This issue affects some unknown processing of the file get_doctor.php. The manipulation of the argument specilizationid leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public 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 confidence

SQL injection vulnerability in Hospital Management System 1.0's get_doctor.php file allows remote attackers to inject malicious SQL queries via the 'specilizationid' parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially extracting sensitive patient data, modifying records, or compromising the entire database.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in get_doctor.php, and conduct a comprehensive code audit to identify and remediate similar SQL injection vulnerabilities throughout the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hospital Management SystemApplication
Affected:= 1.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate get_doctor.php in the web application
    Search the web root directory for the file get_doctor.php. Common paths may include /admin/, /includes/, or the root of the Hospital Management System installation.
    Affected if The file get_doctor.php exists in the application directory structure, indicating the vulnerable component is present.
  2. Identify the 'specilizationid' parameter usage
    Open get_doctor.php and search for the string 'specilizationid' (note the misspelling). Look for how this parameter is used in the code.
    Affected if The file contains code that retrieves the 'specilizationid' parameter from a GET or POST request without verification.
  3. Check for SQL query construction with the parameter
    Examine the SQL query in get_doctor.php that uses the 'specilizationid' parameter. Determine if the query is built by concatenating or interpolating the parameter directly into the SQL string.
    Affected if The SQL query is constructed by directly inserting the 'specilizationid' parameter into the query string without using prepared statements or binding parameters.
  4. Verify input sanitization or prepared statements
    Search the get_doctor.php file for functions like mysqli_prepare, pdo->prepare, htmlspecialchars, mysqli_real_escape_string, or any sanitization functions applied to the 'specilizationid' parameter before the SQL query.
    Affected if No parameterized queries (prepared statements) or input sanitization functions are found protecting the 'specilizationid' parameter in the SQL query.
  5. Confirm the application version is 1.0
    Check the application documentation, footer, or any version file (such as version.php, README, or config files) to verify the installed version of the Fabian Hospital Management System.
    Affected if The installed version of Fabian Hospital Management System is exactly 1.0.

A user is affected if the Fabian Hospital Management System version 1.0 is installed and the get_doctor.php file contains the vulnerable 'specilizationid' parameter used directly in an SQL query without prepared statements or input sanitization.

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

Replace dynamic SQL queries with prepared statements/parameterized queries in get_doctor.php, and conduct a comprehensive code audit to identify and remediate similar SQL injection vulnerabilities throughout the application.

Fix this in Hospital Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10170 — 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-2024-10170 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