# CVE-2025-9313: Unauthorized database access in Asseco mMedica

> Unauthenticated attackers can bypass authentication to gain full access to the database, exposing sensitive data in Asseco mMedica.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-85v2-7wpp-wgf5

## What is CVE-2025-9313?

CVE-2025-9313 is a critical authentication bypass vulnerability in Asseco Poland S.A. mMedica, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated user can connect to a publicly accessible database using arbitrary credentials. The system grants full access to the database by leveraging a previously authenticated connection through a "mmBackup" application. This flaw allows attackers to bypass authentication mechanisms and gain unauthorized access to database with sensitive data.

This issue affects Asseco mMedica in versions before 11.9.5.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2025-9313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9313 is a critical authentication bypass vulnerability in Asseco Poland S.A. mMedica, published on 28 Oct 2025. 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-2025-9313 in the wild and no public exploit code.

Affected product: Asseco Poland S.A. mMedica. 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-9313/ (Markdown: https://insights.sbomify.com/CVE-2025-9313/index.md)
```

## Sources

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

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