dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-44161

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 15 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 manipulation due to cross-site request forgery. The following products are affected: Acronis Cyber Protect 15 (Linux, Windows) before build 35979.

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

Cross-site request forgery (CSRF) vulnerability in Acronis Cyber Protect 15 allows attackers to manipulate sensitive information by tricking authenticated users into executing unintended actions via malicious requests. The lack of proper CSRF tokens or validation on sensitive endpoints enables attackers to perform actions on behalf of legitimate users.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) or SameSite cookie attributes on all state-changing operations. Validate CSRF tokens on the server side for all sensitive requests.

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
Cyber ProtectApplication
Affected:< 15= 15

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 Cyber Protect 15 installation and version
    Check installed version via product management console, PowerShell (Get-WmiObject -Class Win32_Product), or registry keys under HKLM\SOFTWARE\Acronis\Registration. Compare version number against affected ranges: versions < 15 or version = 15 are vulnerable.
    Affected if Installed version is Acronis Cyber Protect 15 (any build within the 15.x branch) or any version number less than 15.
  2. Confirm web management interface is enabled
    Check if the Acronis web-based management console is accessible by attempting to reach the server on typical ports (443, 9876, 9877) or by inspecting services via services.msc for 'Acronis Management Service' or similar web service processes.
    Affected if Web interface is exposed and accessible to users or attackers on the network.
  3. Inspect session cookies for SameSite attribute
    Log into the Acronis management console, open browser developer tools (F12), go to Application > Cookies, and examine all cookies associated with the Acronis domain. Check if 'SameSite' attribute is set to 'Strict' or 'Lax', or if it is missing entirely.
    Affected if Cookies lack SameSite attribute or have SameSite=None without Secure flag, indicating vulnerability to cross-site cookie leakage.
  4. Verify CSRF token implementation on sensitive endpoints
    Use a web proxy (Burp Suite, OWASP ZAP) to capture requests when performing state-changing actions (e.g., creating backups, modifying protection policies, changing user settings). Inspect if each POST/PUT request includes a CSRF token parameter or header, and verify the server validates these tokens on receipt.
    Affected if State-changing requests succeed without requiring a valid CSRF token or anti-CSRF header, confirming lack of server-side validation.

Your environment is affected if you run Acronis Cyber Protect version 15 or lower AND the web interface is accessible AND sensitive operations lack CSRF token validation or SameSite cookie protections.

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

Implement anti-CSRF tokens (synchronizer token pattern) or SameSite cookie attributes on all state-changing operations. Validate CSRF tokens on the server side for all sensitive requests.

Recommended fix Moderate confidence

Acronis Cyber Protect 15 build 35979 or later

  1. 1. Obtain the updated Acronis Cyber Protect 15 installer (build 35979 or later) from the official Acronis download portal or your licensed vendor channel
  2. 2. Review the Acronis upgrade documentation and release notes for build 35979
  3. 3. Ensure you have a valid backup of the current configuration and data
  4. 4. Schedule a maintenance window to minimize business impact
  5. 5. Run the installer and follow the on-screen prompts to upgrade Cyber Protect 15 to build 35979 or later
  6. 6. After upgrade, verify the installation was successful and the web console is accessible
  7. 7. Test critical protection functions to confirm normal operation
Caveat Review Acronis release notes for build 35979 - some legacy features or integrations may require reconfiguration after upgrade

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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