dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-44207

MEDIUM · 5.4 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 15 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 protection plan name. 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 · high confidence

Stored cross-site scripting (XSS) vulnerability in the protection plan name field of Acronis Cyber Protect 15. An authenticated attacker can inject malicious JavaScript code into the protection plan name, which persists in the system and executes when other users view or interact with the affected protection plan.

MitigationUpgrade to Acronis Cyber Protect 15 build 35979 or later. As a compensating control, restrict access to protection plan creation/modification to trusted administrators and implement Content Security Policy headers.

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
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. Identify Acronis Cyber Protect version and build number
    Check the installed version of Acronis Cyber Protect 15 via the management console (Help > About) or system information. Note both the version number (e.g., 15.x.x) and the build number.
    Affected if The installed version is 15 or lower, or the build number is below 35979.
  2. Access protection plan management interface
    Log into the Acronis Cyber Protect management console and navigate to the Protection Plans section, or use the Acronis cmdlet Get-ProtectionPlan if using PowerShell management.
    Affected if User has access to view or create protection plans in the console.
  3. Inspect all protection plan names for XSS payloads
    Review each protection plan name displayed in the console. Look for suspicious patterns including script tags (<script>), javascript: URIs, event handlers (onerror, onload, onmouseover), or unusual HTML characters that could indicate injection.
    Affected if Any protection plan name contains JavaScript code, HTML tags, or encoded script payloads.
  4. Check browser console for XSS errors when viewing plans
    When logged into the Acronis console, open the browser developer console (F12) and navigate to Protection Plans. Watch for any JavaScript errors or unexpected script executions.
    Affected if JavaScript errors appear or scripts execute unexpectedly when viewing protection plan names.

A user is affected if they run Acronis Cyber Protect 15 with build number below 35979 AND have protection plans with malicious script content in their names that can execute when viewed by other users.

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 to Acronis Cyber Protect 15 build 35979 or later. As a compensating control, restrict access to protection plan creation/modification to trusted administrators and implement Content Security Policy headers.

Recommended fix High confidence

Acronis Cyber Protect 15 build 35979 or later

  1. Check current Acronis Cyber Protect 15 version by navigating to Settings > About in the management console
  2. Download Acronis Cyber Protect 15 build 35979 or later from the official Acronis download center or your licensed vendor channel
  3. Review Acronis upgrade documentation for your platform (Linux or Windows) before proceeding
  4. Apply the upgrade following standard Acronis upgrade procedures for your deployment type
  5. After upgrade, verify the version by checking Settings > About shows build 35979 or higher
  6. Test that protection plan names properly sanitize special characters to confirm the XSS fix is applied
Caveat Standard upgrade considerations apply - review Acronis release notes for any configuration or compatibility changes in this build

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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