dbcve.org
Cyber ProtectApplication · Acronis

CVE-2021-38087

MEDIUM · 6.1 CVSS v3.1 Published 2021-08-12
Fix available
A fix is available. Upgrade to 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
Reflected cross-site scripting (XSS) was possible on the login page in Acronis Cyber Protect 15 prior to build 27009.

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

Reflected cross-site scripting (XSS) vulnerability in Acronis Cyber Protect 15 login page allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in the response, leading to potential session hijacking or credential theft. The vulnerability exists in versions prior to build 27009.

MitigationUpgrade Acronis Cyber Protect 15 to build 27009 or later to incorporate vendor-provided input sanitization fixes.

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
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 version
    Open the Acronis Cyber Protect management console or check the installed software version on the server. In the management console, navigate to Help > About or check the installer/registry for the version number.
    Affected if The installed version is 15 or earlier (any version labeled as 15.x or lower)
  2. Check the build number
    In the management console, locate the build number (often displayed alongside the version in Help > About or in the product's installation details). Compare this build number to 27009.
    Affected if The build number is below 27009 (e.g., 26500, 25000, etc.)
  3. Verify login page accessibility
    Access the Acronis Cyber Protect login page via the web interface (typically https://hostname or IP/cp). Attempt to submit test input containing HTML/script tags in the username or password fields to observe if the input is reflected back in the response without sanitization.
    Affected if User-supplied input is reflected back in the page response without being sanitized or encoded, allowing script injection
  4. Confirm product is truly version 15
    Check the exact version string reported by the product. The vulnerability affects version 15 specifically, including any 15.x builds prior to build 27009.
    Affected if The product reports version 15.0.x or version 15 (any build prior to 27009)
  5. Check for recent security updates
    Review the Acronis Cyber Protect update history or changelog for references to CVE-2021-38087 or XSS fixes in the login component. This can confirm whether the build in use includes the vulnerability fix.
    Affected if No security update addressing CVE-2021-38087 has been applied, and the build remains below 27009

You are affected if Acronis Cyber Protect 15 is installed with any build number below 27009 and the login page reflects unsanitized user input in the response.

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

Upgrade Acronis Cyber Protect 15 to build 27009 or later to incorporate vendor-provided input sanitization fixes.

Recommended fix High confidence

Acronis Cyber Protect 15 build 27009 or later

  1. Identify the current build version of Acronis Cyber Protect 15 installation
  2. Upgrade to Acronis Cyber Protect 15 build 27009 or later which contains the security fix for the reflected XSS vulnerability on the login page
  3. Verify the upgrade was successful by confirming the new build number

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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