dbcve.org
Cyber ProtectApplication · Acronis

CVE-2024-55541

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to after 15 or later.
See remediation →
68/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
Stored cross-site scripting (XSS) vulnerability due to missing origin validation in postMessage. The following products are affected: Acronis Cyber Protect 16 (Linux, Windows) before build 39169.

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

Stored cross-site scripting (XSS) vulnerability in Acronis Cyber Protect 16 due to missing origin validation when handling postMessage communications. The vulnerability allows remote attackers to inject malicious scripts that get persisted and executed in the context of other users' browsers when they interact with the affected component.

MitigationUpdate Acronis Cyber Protect 16 to build 39169 or later. Additionally, implement strict origin validation for all postMessage event listeners to verify the sender's origin before processing any messages.

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= 16

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify Acronis Cyber Protect installation version
    Check the installed product version through the management console, or use the Acronis command-line tool (if available) to query the build number. Typically found in the product UI under 'About' or via 'cyber --version' command in the installation directory.
    Affected if The installed version is Acronis Cyber Protect 16 (any build) or version 15 or earlier.
  2. Determine the exact build number
    Locate the specific build version of the installation. In Acronis products, the build number is usually displayed in the management console or can be retrieved via the agent status information.
    Affected if The build number is lower than 39169 (for version 16) or the version is 15/earlier.
  3. Verify web management console accessibility
    Determine if the Acronis web management console is accessible and in use. This vulnerability affects postMessage communications in the browser-based management interface.
    Affected if The web console is accessible and the product version is within the affected range.
  4. Check for postMessage listener configuration
    Inspect browser developer tools on the management console pages to observe postMessage event listeners. Look for message event handlers that process messages without validating the origin property.
    Affected if The console processes postMessage events without strict origin validation (this would require manual code review or penetration testing to confirm).

A user is affected if they are running Acronis Cyber Protect version 16 with build lower than 39169, or version 15 and earlier, and the web management console is 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 a release after 15
Interim mitigation

Update Acronis Cyber Protect 16 to build 39169 or later. Additionally, implement strict origin validation for all postMessage event listeners to verify the sender's origin before processing any messages.

Recommended fix High confidence

Acronis Cyber Protect 16 build 39169 or later

  1. 1. Identify the current build version of Acronis Cyber Protect 16 installed on the system
  2. 2. If the current build is before 39169, download Acronis Cyber Protect 16 build 39169 or later from the official Acronis download center or update server
  3. 3. Follow Acronis standard upgrade procedures to update the installation to the fixed build
  4. 4. After upgrade, verify the installed version is build 39169 or later
  5. 5. Test the postMessage functionality to confirm the XSS vulnerability is remediated
Caveat Review Acronis release notes for build 39169 to check for any configuration or feature changes that may require adjustment

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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