dbcve.org
Cloud ManagerApplication · Acronis

CVE-2023-41746

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to 6.2.23089.203 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Remote command execution due to improper input validation. The following products are affected: Acronis Cloud Manager (Windows) before build 6.2.23089.203.

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

Remote command execution vulnerability in Acronis Cloud Manager for Windows due to improper input validation. This allows unauthenticated attackers to execute arbitrary commands on the affected system. The vulnerability affects versions before build 6.2.23089.203.

MitigationUpgrade Acronis Cloud Manager (Windows) to build 6.2.23089.203 or later. If immediate patching is not possible, restrict network access to the management interface and implement additional input validation at network boundaries.

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
Cloud ManagerApplication
Affected:< 6.2.23089.203

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Cloud Manager is installed
    Check for Acronis Cloud Manager installation directory, typically at C:\Program Files\Acronis\CloudManager or look in Windows Services for 'Acronis Cloud Manager' service
    Affected if Acronis Cloud Manager software is present on the Windows system
  2. Find installed build version
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\CloudManager\, or check the About section in the Acronis Cloud Manager console, or run: Get-ItemProperty 'HKLM:\SOFTWARE\Acronis\CloudManager' | Select-Object Version, Build
    Affected if No build version is returned or the service is not found in registry
  3. Compare build against vulnerable range
    Compare the obtained build number to the affected versions: vulnerable if build < 6.2.23089.203
    Affected if Installed build number is less than 6.2.23089.203
  4. Assess management interface exposure
    Check if the Acronis Cloud Manager management port (default 9877 or configured port) is listening on external interfaces. Run: netstat -an | findstr '9877' or check firewall rules for inbound allowed rules on the management port
    Affected if Management interface port is bound to 0.0.0.0 or accessible from untrusted networks

A system is affected if Acronis Cloud Manager is installed with a build version below 6.2.23089.203 and the management interface is network-accessible.

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 6.2.23089.203 or later
Fixed in 6.2.23089.203
Interim mitigation

Upgrade Acronis Cloud Manager (Windows) to build 6.2.23089.203 or later. If immediate patching is not possible, restrict network access to the management interface and implement additional input validation at network boundaries.

Recommended fix High confidence

6.2.23089.203 or later

  1. 1. Identify all servers running Acronis Cloud Manager for Windows
  2. 2. Check current build version in the Cloud Manager console or via the About section
  3. 3. Download Acronis Cloud Manager version 6.2.23089.203 or later from the official Acronis download center or your licensed portal
  4. 4. Create a full backup of the Cloud Manager database and configuration
  5. 5. Schedule a maintenance window since the upgrade may require service restart
  6. 6. Run the installer for the new version on each affected server
  7. 7. Verify the upgrade was successful by checking the build version after installation
  8. 8. Confirm all Cloud Manager services are running properly
Caveat Review Acronis release notes for any configuration or feature changes between your current version and 6.2.23089.203

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

Fix this in Cloud Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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