# CVE-2025-59102: Secrets Stored in Plaintext in Database in dormakaba access manager

> Attackers can download database backups containing plaintext PINs and sensitive configuration data from dormakaba Access Manager devices.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-8fr2-7cfw-phcg

## What is CVE-2025-59102?

CVE-2025-59102 is a medium-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The web server of the Access Manager offers a functionality to download a backup of the local database stored on the device. This database contains the whole configuration. This includes encrypted MIFARE keys, card data, user PINs and much more. The PINs are even stored unencrypted. Combined with the fact that an attacker can easily get access to the backup functionality by abusing the session management issue (CVE-2025-59101), or by exploiting the weak default password (CVE-2025-59108), or by simply setting a new password without prior authentication via the SOAP API (CVE-2025-59097), it is easily possible to access the sensitive data on the device.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2025-59102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59102 is a medium-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59102 in the wild and no public exploit code.

Affected product: dormakaba Access Manager 92xx-k5. 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-59102/ (Markdown: https://insights.sbomify.com/CVE-2025-59102/index.md)
```

## Sources

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

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