# CVE-2026-6005: code-projects Patient Record Management System hematology_print.php sql injection

> Remote attackers can exploit SQL injection in hematology_print.php to read or modify patient records in the Patient Record Management System.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-9qjr-82wx-8hcx

## What is CVE-2026-6005?

CVE-2026-6005 is a medium-severity SQL injection vulnerability in code-projects Patient Record Management System, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in code-projects Patient Record Management System 1.0. The affected element is an unknown function of the file /hematology_print.php. Executing a manipulation of the argument hem_id can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-6005?


## How do I fix CVE-2026-6005?

No fix has been published for CVE-2026-6005 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6005 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6005 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6005 and fix it if it is affected.

What it is: CVE-2026-6005 is a medium-severity SQL injection vulnerability in code-projects Patient Record Management System, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6005 exists.

Affected product: code-projects Patient Record Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6005/ (Markdown: https://insights.sbomify.com/CVE-2026-6005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6005
- OSV: https://osv.dev/vulnerability/CVE-2026-6005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6005/
Summaries are generated and may contain mistakes; the official description above is the record.