dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-48961

HIGH · 7.3 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 →
73/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 folder permissions. The following products are affected: Acronis Cyber Protect 16 (Windows) before build 39938.

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

Acronis Cyber Protect 16 on Windows prior to build 39938 contains insecure folder permissions that allow a local authenticated attacker to escalate privileges to administrator level by modifying executable files or folder locations used by the service.

MitigationApply Acronis Cyber Protect 16 update to build 39938 or later to remediate the folder permission 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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/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. Verify Acronis Cyber Protect 16 is installed
    Check for the Acronis Cyber Protect 16 service or installation by running 'Get-Service | Where-Object {$_.DisplayName -like "*Acronis*"}' in PowerShell, or look for the installation directory typically at C:\Program Files\Acronis
    Affected if Acronis Cyber Protect 16 service or installation is found on the system
  2. Identify the installed build version
    Check the version by opening Acronis Cyber Protect 16 and navigating to Help > About, or query the Windows Registry at HKLM\SOFTWARE\Acronis\Global\Install\Build, or check the executable version of a core component like C:\Program Files\Acronis\Cyber Protect\bin\service_host.exe
    Affected if The build version number is lower than 39938
  3. Locate service executable folders
    Identify folders containing executable files used by Acronis services. Common locations include C:\Program Files\Acronis\Cyber Protect\, C:\ProgramData\Acronis\, and subfolders under the installation directory that contain .exe files used by the service
    Affected if Acronis service folders exist on the system
  4. Inspect folder permissions for weak ACLs
    Right-click on Acronis program folders, go to Properties > Security tab, and check the permissions. Specifically examine if 'Authenticated Users' or 'Users' group has 'Modify' or 'Full Control' permissions on folders containing executables. Use PowerShell command: 'Get-Acl "C:\Program Files\Acronis\*" | Select-Object Path, AccessToString' to enumerate ACLs
    Affected if Authenticated users or non-admin users have Write or Modify permissions on folders containing Acronis service executables

The system is affected if Acronis Cyber Protect 16 is installed with a build version prior to 39938 AND folder permissions allow authenticated users to modify executable files or folders used by the service.

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

Apply Acronis Cyber Protect 16 update to build 39938 or later to remediate the folder permission vulnerability.

Recommended fix Moderate confidence

Acronis Cyber Protect 16 build 39938 or later

  1. Obtain the updated installer for Acronis Cyber Protect 16 build 39938 or later from the official Acronis download center or your licensed vendor portal
  2. Ensure you have appropriate administrator privileges on the target Windows system
  3. Backup current Acronis Cyber Protect 16 configuration and any critical data
  4. Run the Acronis Cyber Protect 16 installer with elevated (administrator) privileges
  5. Follow the on-screen installation wizard to complete the upgrade to build 39938 or newer
  6. Verify the installation completed successfully by checking the build version in the Acronis Cyber Protect console
  7. Confirm that folder permissions have been corrected by reviewing the installation directory permissions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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