CVE-2023-48679
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 · uneditedStored 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 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 · moderate confidenceStored cross-site scripting (XSS) vulnerability in Acronis Cyber Protect 16 due to missing origin validation in postMessage communications. Attackers can inject malicious scripts that persist and execute when users interact with the vulnerable component.
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< 16CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Acronis Cyber Protect installationCheck for Acronis Cyber Protect service or installed software: On Windows, run 'Get-Service | Where-Object {$_.DisplayName -like "*Acronis*"}' or check Programs and Features. On Linux, run 'ps aux | grep acronis' or check installed packages.Affected if Acronis Cyber Protect is not installed on the system
-
Identify installed version and build numberCheck the installed version via the management console (About section), registry key 'HKLM\SOFTWARE\Acronis\Global\Version', or by running 'C:\Program Files\Acronis\CompareAndCopy\version.exe' if present. Record both the major version and build number.Affected if The build number is below 37391, indicating an unpatched version
-
Verify web management interface is accessibleAccess the Acronis Cyber Protect management console web interface (typically https://localhost:9877 or the configured management server URL). Attempt to load the dashboard and observe if the web interface responds.Affected if The web interface is accessible and the product version is below build 37391
-
Inspect postMessage handler configuration (if accessible)If you have access to the web interface source files, examine JavaScript files in the management console web directory for postMessage event listeners that lack origin validation. Look for code patterns like 'window.addEventListener("message", function(event){...})' without 'event.origin' checks.Affected if postMessage handlers lack origin validation and the product version is below build 37391
The environment is affected if Acronis Cyber Protect is installed with a build number below 37391 and the web management interface is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16
Upgrade Acronis Cyber Protect 16 to build 37391 or later. Alternatively, implement strict origin validation for all postMessage event handlers to verify message sender identity before processing.
Acronis Cyber Protect 16 build 37391 or later
- 1. Back up all critical data and verify backup integrity before proceeding with the upgrade.
- 2. Download Acronis Cyber Protect 16 from the official Acronis download center or your licensed vendor portal.
- 3. Ensure the version you download is build 37391 or later.
- 4. Follow the standard Acronis upgrade installation procedure for your platform (Linux or Windows).
- 5. During installation, select the upgrade/in-place update option to preserve existing configuration and data.
- 6. After installation completes, verify the build number by checking About or System Information in the Cyber Protect console.
- 7. Confirm the installed build number is 37391 or higher.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-48679 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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