dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11501

HIGH · 7.3 CVSS v3.1 Published 2026-06-08
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 security flaw has been discovered in SourceCodester Hospitals Patient Records Management System 1.0. This issue affects some unknown processing of the file /classes/Master.php?f=save_patient. The manipulation of the argument ID results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may 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 · high confidence

A SQL injection vulnerability exists in the save_patient function of Master.php in SourceCodester Hospitals Patient Records Management System 1.0. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through the /classes/Master.php?f=save_patient endpoint.

MitigationImplement prepared statements/parameterized queries for the ID parameter in the save_patient function to prevent SQL injection, and validate/sanitize all user inputs.

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 SourceCodester Hospitals Patient Records Management System is installed
    Locate the web application directory or check for the presence of the file structure typical of this PHP application. Look for typical markers like login pages, hospital-related content, or the /classes directory.
    Affected if The application is present and appears to be the SourceCodester Hospitals Patient Records Management System.
  2. Verify the application version is 1.0
    Check the application for a version identifier. This may be in a config file, about page, or version comment in source files. Compare your installed version against the affected version 1.0.
    Affected if The installed version is Hospitals Patient Records Management System 1.0.
  3. Locate and inspect the vulnerable file /classes/Master.php
    Navigate to the /classes directory in the web application root and open Master.php. Look for the save_patient function definition.
    Affected if The file /classes/Master.php exists and contains a save_patient function.
  4. Examine the save_patient function for SQL injection vulnerability
    Within the save_patient function in Master.php, search for database query execution (such as mysqli_query, $conn->query, or similar) that incorporates the ID parameter directly without parameterized queries or proper escaping. Look for patterns like WHERE id='$id' or similar unsanitized concatenation.
    Affected if The save_patient function builds SQL queries using the ID parameter without using prepared statements or parameter binding.
  5. Determine if the application is network-accessible
    Verify whether the web application is accessible over the network (local or remote). This could be via browser access to the application's URL or checking web server configuration.
    Affected if The application is accessible via HTTP/HTTPS, making the SQL injection potentially exploitable remotely.

A user is affected if they have SourceCodesters Hospitals Patient Records Management System version 1.0 deployed with the vulnerable save_patient function in /classes/Master.php that uses unsanitized ID parameter in SQL queries.

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 the ID parameter in the save_patient function to prevent SQL injection, and validate/sanitize all user inputs.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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