dbcve.org
BeedriveApplication · Synology

CVE-2025-54159

HIGH · 7.5 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 1.4.2-13960 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Missing authorization vulnerability in BeeDrive in Synology BeeDrive for desktop before 1.4.2-13960 allows remote attackers to delete arbitrary files via unspecified vectors.

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 · moderate confidence

A missing authorization check in Synology BeeDrive for desktop versions prior to 1.4.2-13960 allows unauthenticated remote attackers to delete arbitrary files on the affected system. The vulnerability stems from insufficient access control validation in file deletion operations, enabling attackers to exploit the application without credentials.

MitigationUpgrade BeeDrive for desktop to version 1.4.2-13960 or later to apply the authorization fix. Review file permissions and network exposure of systems running BeeDrive until the patch is deployed.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BeedriveApplication
Affected:< 1.4.2-13960

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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. Confirm BeeDrive installation
    On Windows, check Program Files or Program Files (x86) for a 'BeeDrive' folder, or search for 'BeeDrive' in Add/Remove Programs. On macOS, check /Applications for BeeDrive.app or run 'ls /Applications | grep -i beedrive'.
    Affected if BeeDrive is found installed on the system
  2. Identify installed version
    On Windows, right-click the BeeDrive executable in the installation folder and select Properties > Details to view the File Version. On macOS, right-click BeeDrive.app > Get Info to view the Version. Alternatively, launch BeeDrive and look for the version number in the About or Settings section.
    Affected if The version number is lower than 1.4.2-13960
  3. Verify if BeeDrive service is running
    On Windows, open Task Manager and look for 'BeeDrive.exe' in the Processes tab, or check Services for 'BeeDrive Service'. On macOS, run 'ps aux | grep -i beedrive' in Terminal.
    Affected if BeeDrive is actively running as a service or background process
  4. Check network exposure
    On Windows, run 'netstat -an | findstr LISTENING' in Command Prompt to list listening ports. Look for ports associated with BeeDrive (commonly 8080, 9123, or similar). On macOS, run 'lsof -i -P | grep -i listen' in Terminal.
    Affected if BeeDrive is listening on network-accessible ports (indicating potential remote attack surface)

If BeeDrive is installed with a version prior to 1.4.2-13960 and the service is running (especially with network exposure), the system is affected by this missing authorization vulnerability allowing unauthenticated remote file deletion.

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.

dbcve · scoped
Upgrade available Upgrade to 1.4.2-13960 or later
Fixed in 1.4.2-13960
Interim mitigation

Upgrade BeeDrive for desktop to version 1.4.2-13960 or later to apply the authorization fix. Review file permissions and network exposure of systems running BeeDrive until the patch is deployed.

Recommended fix High confidence

1.4.2-13960

  1. 1. Open Synology BeeDrive desktop application
  2. 2. Navigate to Help > About to check current installed version
  3. 3. If version is below 1.4.2-13960, download the latest version from the official Synology website at www.synology.com
  4. 4. Run the installer and follow the on-screen prompts to upgrade BeeDrive to version 1.4.2-13960 or later
  5. 5. After installation completes, verify the version in Help > About shows 1.4.2-13960 or higher
  6. 6. Restart the BeeDrive application if not done automatically

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Beedrive Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54159 — 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-54159 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