dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-30408

MEDIUM · 6.7 CVSS v3.0 Published 2025-04-24
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 folder permissions. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 39904, 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

Local privilege escalation vulnerability in Acronis Cyber Protect Windows agents caused by insecure folder permissions on the installation directory. Low-privileged users can modify executable or configuration files that the service runs with elevated privileges, leading to privilege escalation.

MitigationApply vendor patches (build 39904 for Cloud Agent, build 39938 for Cyber Protect 16) which remediate the permission issues, or manually restrict folder permissions on the affected installation directories to prevent non-admin modification of sensitive files.

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. Confirm Acronis Cyber Protect agent installation and version
    Open Registry Editor and navigate to HKLM\SOFTWARE\Acronis\Agent\Info, or run: Get-ItemProperty 'HKLM:\SOFTWARE\Acronis\Agent\Info' | Select-Object Version, ProductVersion. Also check HKLM\SOFTWARE\Acronis\MMS\Info for the Build number.
    Affected if The installed version has a build number lower than 39904 (Cloud Agent) or 39938 (Cyber Protect 16), or the version cannot be determined.
  2. Identify the installation directory
    Check the registry key HKLM\SYSTEM\CurrentControlSet\Services\AcronisAgent\ImagePath, or run: (Get-WmiObject win32_service | Where-Object {$_.Name -like '*Acronis*'}).PathName to find the executable path.
    Affected if The agent is installed in a directory that exists on the system.
  3. Verify the service runs with elevated privileges
    Run: Get-WmiObject win32_service | Where-Object {$_.Name -match 'Acronis'} | Select-Object Name, StartName, State. Check if StartName is 'LocalSystem' or contains 'SYSTEM' or 'Administrator'.
    Affected if The Acronis service runs with elevated privileges (LocalSystem, SYSTEM, or Administrator account).
  4. Check folder permissions on the installation directory
    Open Command Prompt as a non-admin user and run: icacls "C:\Program Files\Acronis" (or the identified installation path). Alternatively, run PowerShell: Get-Acl 'C:\Program Files\Acronis' | Format-List.
    Affected if Non-admin users have modify, write, or full control permissions (flags like '(F)', '(M)', '(W)', or '(D,DC)' appear in the icacls output for Users or Authenticated Users).
  5. Verify low-privileged user can modify executable or config files
    As a standard (non-admin) user, attempt to create or modify a test file in the installation directory, or run: icacls "C:\Program Files\Acronis\*.exe" to see who has write access to executable files.
    Affected if Standard users or Authenticated Users have write or modify permissions to .exe, .dll, or .config files in the installation directory.

A user is affected if the Acronis Cyber Protect agent is installed with a build lower than 39904/39938 AND the installation directory grants low-privileged users modify access to files that run with SYSTEM privileges.

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 vendor patches (build 39904 for Cloud Agent, build 39938 for Cyber Protect 16) which remediate the permission issues, or manually restrict folder permissions on the affected installation directories to prevent non-admin modification of sensitive files.

Recommended fix Moderate confidence

Acronis Cyber Protect Cloud Agent: build 39904+; Acronis Cyber Protect 16: build 39938+

  1. Identify the currently installed Acronis product and its build version
  2. For Acronis Cyber Protect Cloud Agent (Windows): upgrade to build 39904 or later
  3. For Acronis Cyber Protect 16 (Windows): upgrade to build 39938 or later
  4. Verify the upgrade was successful by confirming the new build number in the product UI or via command line
Caveat Standard upgrade considerations apply - test in non-production environment first, ensure backup of configuration exists

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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