Cyber Resilience

CVE-2025-54158

Access Control in Synology Beedrive ≤ 1.4.2-13960

Published
04 December 2025
Modified
24 February 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0018 7th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-54158 is a high-severity Missing Authentication for Critical Function (CWE-306) vulnerability in Synology Beedrive. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Missing authentication for critical function vulnerability in BeeDrive in Synology BeeDrive for desktop before 1.4.2-13960 allows local users to execute arbitrary code via unspecified vectors.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-52945Same product: Synology Beedrive
CVE-2025-54160Same product: Synology Beedrive
CVE-2025-54159Same product: Synology Beedrive
CVE-2024-11399Same product: Synology Beedrive
CVE-2024-50630Same product class: NAS / storage appliance
CVE-2023-52949Same product class: NAS / storage appliance
CVE-2023-52947Same product class: NAS / storage appliance
CVE-2024-53281Same product class: NAS / storage appliance
CVE-2025-29846Same product class: NAS / storage appliance
CVE-2023-52951Same product class: NAS / storage appliance

Affected Assets

synology
beedrive
≤ 1.4.2-13960

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • IA-2 Identification and Authentication (Organizational Users)
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.3
  • V6.4.4
  • V10.4.16
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authentication checks before permitting execution of critical functions, blocking the unauthenticated local code execution path in BeeDrive.

prevent

Restricts local user privileges so that even if a critical function lacks authentication, the user cannot reach arbitrary code execution.

prevent

Requires identification and authentication of users before allowing access to application functions, directly addressing the missing-authentication flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 full match
prevents

Directly requires authentication of users/services/hardware, which eliminates missing authentication for critical functions.

PR.AA-01 partial match
prevents

Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.

PR.AA-05 partial match
prevents

Defining and enforcing authorizations assumes prior authentication and therefore only partially mitigates the absence of authentication.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized access can be undermined by missing authentication but does not address the root authentication gap.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

The control explicitly calls for authentication before any critical function is reached, eliminating the possibility of bypassing authentication for high-value operations.

prevents

Mandating authentication requirements for critical functions at the requirements-gathering stage ensures that essential operations are not left unprotected by missing login or verification mechanisms.

mitigates

Mandating authentication for network services and critical functions stops attackers from invoking sensitive operations without credentials, closing gaps where authentication is absent for important capabilities.

prevents

Security engineering principles insist on authentication and authorization for every critical function, eliminating entry points that lack any access control mechanism.

none

Requiring strong authentication and access-privilege enablement for remote connections ensures that critical functions cannot be invoked without proper verification, closing a gap that would otherwise allow unauthenticated use.

none

Mandatory use of access cards, biometrics, or two-factor authentication ensures that critical physical areas cannot be entered without proper authentication.

References