dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-48959

MEDIUM · 6.7 CVSS v3.0 Published 2025-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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
Local privilege escalation due to insecure file permissions. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 40077.

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

Local privilege escalation vulnerability in Acronis Cyber Protect Cloud Agent for Windows caused by insecure file permissions. An authenticated local attacker could exploit misconfigured file permissions to gain elevated privileges on the affected system. The vulnerability exists in versions before build 40077.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 40077 or later to remediate the insecure file permissions vulnerability.

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

CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/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. Identify if Acronis Cyber Protect Cloud Agent for Windows is installed
    Open Programs and Features (appwiz.cpl) or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Acronis Cyber Protect Cloud Agent or similar Acronis protection agent
    Affected if The Acronis Cyber Protect Cloud Agent for Windows is present on the system
  2. Locate the Acronis agent installation directory
    Check common installation paths such as C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\, or right-click the installed program in Programs and Features and select Properties to find the installation location
    Affected if The installation directory exists (typically under Program Files\Acronis)
  3. Determine the installed build version
    Open the Acronis agent's About or Help section within the management console, or check the version info of the main executable file (often named something like agent.exe or backup.exe) in the installation directory by right-clicking the file and viewing Properties > Details
    Affected if The build version is lower than 40077 (the version displayed will show a build number that can be compared
  4. Verify file permissions on the Acronis installation directory
    Right-click the main Acronis installation folder, select Properties > Security, and examine which users and groups have Write or Full Control permissions. Particularly check if non-admin users have modify/write access to executable files or configuration files
    Affected if Non-privileged users have Write or Modify permissions to executable files or sensitive configuration files in the Acronis installation directory

The system is affected if Acronis Cyber Protect Cloud Agent for Windows is installed with a build version lower than 40077, and non-administrative users have write access to the agent's executable files or configuration files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis Cyber Protect Cloud Agent to build 40077 or later to remediate the insecure file permissions vulnerability.

Recommended fix Moderate confidence

Acronis Cyber Protect Cloud Agent (Windows) build 40077 or later

  1. Verify the currently installed Acronis Cyber Protect Cloud Agent version on the Windows system
  2. Download the latest Acronis Cyber Protect Cloud Agent installer (build 40077 or later) from the official Acronis download center or management console
  3. Stop the Acronis Agent service on the Windows machine before upgrading
  4. Run the installer with administrative privileges to upgrade the agent
  5. Restart the Windows system or restart the Acronis Agent service after installation completes
  6. Verify the agent version has been updated to build 40077 or later

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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