# CVE-2024-1228: Hardcoded password in Eurosoft Przychodnia

> Attackers can access sensitive patient data using a hardcoded database password present in all installations of Eurosoft Przychodnia.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:H/SA:H/AU:Y/R:U/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2024
- **Updated:** 7 Oct 2025
- **Also known as:** GHSA-v5m7-r9rr-hxp7

## What is CVE-2024-1228?

CVE-2024-1228 is a critical vulnerability in Eurosoft Przychodnia, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use of hard-coded password to the patients' database allows an attacker to retrieve sensitive data stored in the database. The password is the same among all Eurosoft Przychodnia installations.

This issue affects Eurosoft Przychodnia software before version 20240417.001 (from that version vulnerability is fixed).

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2024-1228?

It affects 1 product.


Products: Eurosoft Przychodnia.

## How do I fix CVE-2024-1228?

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

## Is CVE-2024-1228 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1228 and fix it if it is affected.

What it is: CVE-2024-1228 is a critical vulnerability in Eurosoft Przychodnia, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1228 in the wild and no public exploit code.

Affected product: Eurosoft Przychodnia. 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-2024-1228/ (Markdown: https://insights.sbomify.com/CVE-2024-1228/index.md)
```

## Sources

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

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