dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-48682

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-27
Fix available
A fix is available. Upgrade to 16 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 in unit name. The following products are affected: Acronis Cyber Protect 16 (Linux, Windows) before build 37391.

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

A stored cross-site scripting (XSS) vulnerability exists in the unit name field of Acronis Cyber Protect 16. This allows an attacker to inject malicious JavaScript code into the unit name which persists on the server and executes in the browsers of other users who view or interact with the affected unit name.

MitigationUpdate Acronis Cyber Protect 16 to build 37391 or later. Additionally, implement output encoding and input validation on the unit name field to prevent XSS exploitation.

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:< 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Acronis Cyber Protect installation
    Check if Acronis Cyber Protect is installed on the system by looking for the installation directory (typically C:\Program Files\Acronis\ or /usr/local/acronis/) or checking installed programs via system utility.
    Affected if Acronis Cyber Protect software is present on the system.
  2. Determine installed version
    Locate the version information - commonly found in the About section of the management console, or check the installed software details via Windows Programs and Features, or inspect version files in the installation directory.
    Affected if The installed version is below build 37391 (any version less than 16 with build number below 37391).
  3. Verify management interface accessibility
    Access the Acronis Cyber Protect management console (typically via web browser on port 9877 or 443) and navigate to the units or devices management section where unit names are configured.
    Affected if The management console is accessible and the unit name configuration interface is available.
  4. Check unit name configuration
    In the management console, view the unit or device list and inspect the unit name field for any existing entries - look for unusual characters or scripts that may indicate prior exploitation.
    Affected if Unit names contain unexpected HTML or JavaScript content, indicating possible exploitation of this XSS vulnerability.

A system is affected if Acronis Cyber Protect 16 is installed with a build number below 37391 and the management console with unit name configuration 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 16 or later
Fixed in 16
Interim mitigation

Update Acronis Cyber Protect 16 to build 37391 or later. Additionally, implement output encoding and input validation on the unit name field to prevent XSS exploitation.

Recommended fix Moderate confidence

Acronis Cyber Protect 16 build 37391 or later

  1. 1. Back up your current Acronis Cyber Protect 16 configuration and data
  2. 2. Download the latest Acronis Cyber Protect 16 installer from the official Acronis download center or your licensed portal
  3. 3. Ensure the installer version is build 37391 or later
  4. 4. Apply the update following Acronis standard upgrade procedures for your Linux or Windows deployment
  5. 5. After upgrade, verify the unit name field properly sanitizes input to prevent XSS

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,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 $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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