dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-59100

MEDIUM · 5.9 CVSS v4.0 Published 2026-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. The database includes sensitive data like passwords, card pins, encrypted Mifare sitekeys and much more.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The web interface of the device includes a database export function for an internal SQLite database containing sensitive information (passwords, card PINs, encrypted Mifare sitekeys). After export, the device is supposed to delete the exported file following a reboot, but this deletion fails when the device does not reboot or due to other unknown conditions. The exported database file remains accessible on the device at a known or discoverable path without any authentication, allowing unauthenticated attackers to download the sensitive database.

MitigationImplement proper access controls or authentication requirements on the export file path, and ensure the exported database is deleted immediately after export regardless of device reboot state, or use secure temporary storage with automatic cleanup.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify database export functionality
    Review the device web interface for a database export or backup feature, typically found in settings, administration, or maintenance sections. Look for options labeled 'export database', 'backup', 'download database', or similar.
    Affected if The device web interface includes a feature to export an internal SQLite database containing sensitive information.
  2. Locate exported database files on the device
    Search the device filesystem for SQLite database files (.db, .sqlite, .sqlite3) in common web-accessible directories such as /tmp, /var/tmp, /www, /web, /downloads, or the web root. Use file listing commands or check known export paths if documented.
    Affected if An exported SQLite database file exists on the device filesystem in a web-accessible location.
  3. Verify unauthenticated access to the exported file
    Attempt to access the discovered database file via HTTP/HTTPS using the device's IP address without providing any login credentials. For example: http://<device-ip>/path/to/exportedfile.db
    Affected if The exported database file is accessible and downloadable without any authentication or authorization.
  4. Confirm sensitive data in the exported file
    Open the exported database file using sqlite3 or a database viewer and inspect its contents for sensitive fields such as passwords, PINs, card data, encryption keys, or sitekeys. Run queries like '.tables' and 'SELECT * FROM <table>' to enumerate data.
    Affected if The exported file contains unencrypted or decryptable sensitive information including passwords, card PINs, or Mifare sitekeys.
  5. Check file age for failed cleanup
    Review the modification timestamp of the exported database file. If the file timestamp is significantly older than the last device reboot or export operation, cleanup likely failed.
    Affected if The exported database file persists on the filesystem beyond the expected deletion window, indicating the cleanup mechanism failed.

A user is affected if their device web interface has a database export feature and an accessible SQLite database file containing sensitive information exists on the device without authentication protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper access controls or authentication requirements on the export file path, and ensure the exported database is deleted immediately after export regardless of device reboot state, or use secure temporary storage with automatic cleanup.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59100 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data