# CVE-2023-6518: Password Disclosure in Mia Technology's Mia-Med

> Attackers can extract plaintext passwords from the executable, compromising user credentials in Mia-Med medical software.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2024
- **Updated:** 20 May 2026
- **Also known as:** GHSA-rm4j-xw99-x97h

## What is CVE-2023-6518?

CVE-2023-6518 is a high-severity vulnerability in MİA-MED, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Plaintext Storage of a Password vulnerability in Mia Technology Inc. MİA-MED allows Read Sensitive Strings Within an Executable.

This issue affects MİA-MED: before 1.0.7.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2023-6518?

It affects 1 product.


Products: Miateknoloji Mia-Med.

## How do I fix CVE-2023-6518?

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

## Is CVE-2023-6518 being exploited?

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

## Other vulnerabilities in MİA-MED

- [CVE-2022-3760](https://insights.sbomify.com/CVE-2022-3760/): SQLi in Mia-Med (critical 9.8)
- [CVE-2023-6515](https://insights.sbomify.com/CVE-2023-6515/): IDOR in Mia Technology's Mia-Med (high 8.8)
- [CVE-2023-6517](https://insights.sbomify.com/CVE-2023-6517/): Seeing the SMS Verification Code in Mia Technology's Mia-Med (high 7.5)
- [CVE-2023-6519](https://insights.sbomify.com/CVE-2023-6519/): Seeing admin password hash value in Mia Technology's Mia-Med (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6518 and fix it if it is affected.

What it is: CVE-2023-6518 is a high-severity vulnerability in MİA-MED, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6518 in the wild and no public exploit code.

Affected product: MİA-MED. 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-2023-6518/ (Markdown: https://insights.sbomify.com/CVE-2023-6518/index.md)
```

## Sources

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

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