{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59100 is a medium-severity missing authorization vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-59100 and fix it if it is affected.\n\nWhat it is: CVE-2025-59100 is a medium-severity missing authorization vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-59100 in the wild and no public exploit code.\n\nAffected product: dormakaba Access Manager 92xx-k5. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59100/ (Markdown: https://insights.sbomify.com/CVE-2025-59100/index.md)","id":"CVE-2025-59100","markdown":"https://insights.sbomify.com/CVE-2025-59100/index.md","name":"CVE-2025-59100","record":{"aliases":["GHSA-78gg-x59j-472c"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Access control system","requires_auth":"none","summary":"Unauthenticated attackers can access exported SQLite databases containing sensitive credentials if the device fails to delete them after export.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SEC-VLab","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"The web interface offers a functionality to export the internal SQLite database. After executing the database export, an automatic download is started and the device reboots. After rebooting, the exported database is deleted and cannot be accessed anymore. However, it was noticed that sometimes the device does not reboot and therefore the exported database is not deleted, or the device reboots and the export is not deleted for unknown reasons. The path where the database export is located can be accessed without prior authentication. This leads to the fact that an attacker might be able to get access to the exported database without prior authentication. \nThe database includes sensitive data like passwords, card pins, encrypted Mifare sitekeys and much more.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Unauthenticated Access to the SQLite Database in dormakaba access manager","id":"CVE-2025-59100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Insufficient Session Management in dormakaba access manager","id":"CVE-2025-59101"},"packages":[],"prev":{"headline":"Unauthenticated Path Traversal in dormakaba access manager","id":"CVE-2025-59099"},"products":["Access Manager 92xx-k5"],"published":"2026-01-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-26","vendors":["dormakaba"]},"summary":"Unauthenticated attackers can access exported SQLite databases containing sensitive credentials if the device fails to delete them after export.","url":"https://insights.sbomify.com/CVE-2025-59100/"}