dbcve.org
BeedriveApplication · Synology

CVE-2025-8074

MEDIUM · 5.6 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 1.4.3-13973 or later.
See remediation →
56/100
Remediation priority · Elevated

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
Origin validation error vulnerability in BeeDrive in Synology BeeDrive for desktop before 1.4.3-13973 allows local users to write arbitrary files with non-sensitive information 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 · high confidence

This is an origin validation error in Synology BeeDrive for desktop versions prior to 1.4.3-13973. The vulnerability allows local authenticated users to write arbitrary files with non-sensitive information to the filesystem, likely due to insufficient validation of file paths or destinations during file operations.

MitigationUpdate BeeDrive for desktop to version 1.4.3-13973 or later to obtain the vendor patch that addresses the origin validation error.

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.3-13973

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

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

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. Locate BeeDrive installation directory
    Check common installation paths: %ProgramFiles%\Synology\BeeDrive or %LocalAppData%\Synology\BeeDrive. Look for BeeDrive.exe and check its file properties for version information.
    Affected if The installed version is earlier than 1.4.3-13973 or version cannot be determined.
  2. Identify installed BeeDrive version
    Right-click on BeeDrive.exe, select Properties, then view the Details tab to find the Product Version. Alternatively, open Control Panel > Programs and Features and locate Synology BeeDrive in the installed programs list.
    Affected if The displayed version number is less than 1.4.3-13973.
  3. Verify BeeDrive is running or scheduled to run
    Open Task Manager and check for BeeDrive.exe in the Processes tab, or check the system tray for the BeeDrive icon. Also verify if BeeDrive is set to start automatically at login via its settings.
    Affected if BeeDrive is currently running or configured to run at startup on the affected version.
  4. Check file sync configuration
    Open the BeeDrive desktop application and navigate to Settings or Preferences. Look for sync folder locations, file transfer settings, or any configuration related to file write operations.
    Affected if Sync folders are configured and the application has write access to local directories.

You are affected if Synology BeeDrive for desktop is installed with a version number lower than 1.4.3-13973 and the application is running or configured to run, as the vulnerability requires the file operation functionality to be active.

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.3-13973 or later
Fixed in 1.4.3-13973
Interim mitigation

Update BeeDrive for desktop to version 1.4.3-13973 or later to obtain the vendor patch that addresses the origin validation error.

Recommended fix High confidence

1.4.3-13973

  1. Verify current BeeDrive version by opening BeeDrive desktop application and navigating to Help > About
  2. Download the latest BeeDrive for desktop version (1.4.3-13973 or later) from the official Synology website
  3. Close the BeeDrive application completely before upgrading
  4. Run the downloaded installer and follow the on-screen prompts to complete the upgrade
  5. Restart the system if prompted and verify the new version is installed

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

Fix this in Beedrive Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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