# CVE-2025-41004: Multiple vulnerabilities in Imaster products Open configuration options

> Attackers can exploit SQL injection in the complaints endpoint to read or modify patient records in Imaster's system.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 12 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-qc32-mjp2-qfv5

## What is CVE-2025-41004?

CVE-2025-41004 is a high-severity SQL injection vulnerability in Imaster Patient Record Management System, published on 12 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Imaster's Patient Records Management System is vulnerable to SQL Injection in the endpoint ‘/projects/hospital/admin/complaints.php’ through the ‘id’ parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-41004?


## How do I fix CVE-2025-41004?

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

## Is CVE-2025-41004 being exploited?

There is no known exploitation of CVE-2025-41004 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41004 and fix it if it is affected.

What it is: CVE-2025-41004 is a high-severity SQL injection vulnerability in Imaster Patient Record Management System, published on 12 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41004 in the wild and no public exploit code.

Affected product: Imaster 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-2025-41004/ (Markdown: https://insights.sbomify.com/CVE-2025-41004/index.md)
```

## Sources

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

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