dbcve.org
AgentApplication · Acronis

CVE-2023-48676

HIGH · 7.1 CVSS v3.1 Published 2023-12-14
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
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
Sensitive information disclosure and manipulation due to missing authorization. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 36943.

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

Missing authorization vulnerability in Acronis Cyber Protect Cloud Agent for Windows (before build 36943) allows unauthenticated attackers to bypass access controls, leading to disclosure of sensitive information and potential data manipulation.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 36943 or later to implement proper authorization checks.

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
AgentApplication
Affected:< c23.12

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 Agent is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject Win32_Product | Where-Object {$_.Name -like "*Acronis*"}' in PowerShell, to list installed Acronis software.
    Affected if No Acronis Cyber Protect Cloud Agent appears in the installed programs list, then the system is not affected by this specific vulnerability.
  2. Locate the Acronis Agent executable
    Navigate to the installation directory, typically C:\Program Files\Acronis\Agent\, or run 'Get-Service | Where-Object {$_.DisplayName -like "*Acronis*"}' in PowerShell to find the running service and its executable path.
    Affected if If the service does not exist or the directory is not present, the agent is not installed and this vulnerability does not apply.
  3. Retrieve the agent build version
    Right-click the Acronis Agent executable (commonly agent.exe or a sub-executable in the bin folder) in the installation directory, select Properties, and check the File version or Product version field. Alternatively, run '(Get-Item "C:\Program Files\Acronis\Agent\bin\agent.exe").VersionInfo' in PowerShell if the path matches your installation.
    Affected if The build number shown is below 36943, indicating the installed version is vulnerable to the authorization bypass.
  4. Confirm version format matches c23.12
    Compare your retrieved build number against the c23.12 release identifier. The agent version may also be displayed in the Acronis Cyber Protect console under the agent details or system information panel.
    Affected if The installed version is earlier than the c23.12 release (which maps to build 36943 or later), meaning the missing authorization check is present.

A Windows system running Acronis Cyber Protect Cloud Agent with a build number below 36943 (or version earlier than c23.12) is affected by this missing authorization vulnerability.

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 36943 or later to implement proper authorization checks.

Recommended fix High confidence

c23.12 (build 36943 or later)

  1. Identify the currently installed Acronis Cyber Protect Cloud Agent version on the Windows system
  2. Access the Acronis official download center or your licensed Acronis account to obtain version c23.12 (build 36943 or later)
  3. Stop any running Acronis services or disable active protection temporarily if required by the upgrade procedure
  4. Run the installer for Acronis Cyber Protect Cloud Agent version c23.12 or higher
  5. Follow the on-screen prompts to complete the upgrade installation
  6. Restart the system if prompted by the installer
  7. Verify the installed version shows build 36943 or later, confirming the patch has been applied

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

Fix this in Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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