dbcve.org
Cyber FilesApplication · Acronis

CVE-2024-49386

MEDIUM · 5.7 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 9.0 or later.
See remediation →
60/100
Remediation priority · Elevated
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
Sensitive information disclosure due to spell-jacking. The following products are affected: Acronis Cyber Files (Windows) before build 9.0.0x24.

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

Acronis Cyber Files for Windows contains a spell-jacking vulnerability where the built-in spell-checking functionality inadvertently transmits typed content (potentially including sensitive data such as credentials, PII, or confidential information) to external spell-check services or captures it in logs, leading to information disclosure.

MitigationUpgrade Acronis Cyber Files Windows to build 9.0.0x24 or later. As an interim measure, disable third-party spell-checking integrations or network-based spell services within the application if such controls are available.

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 FilesApplication
Affected:< 9.0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Verify Acronis Cyber Files is installed
    Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Acronis Cyber Files' or look in C:\Program Files\Acronis\CyberFiles for the application directory.
    Affected if The application is present on the system.
  2. Determine installed version
    Open the Windows Registry key HKLM\SOFTWARE\Acronis\Cyber Files\ or check the application's About/Version dialog if accessible. Note the full version number (e.g., 8.x.x.x).
    Affected if The version number is below 9.0 (for example 8.5.x, 8.0.x, etc.).
  3. Inspect spell-check configuration
    Search for configuration files in the application data folder (typically under %PROGRAMDATA%\Acronis\Cyber Files\ or %APPDATA%\Acronis\Cyber Files\) for settings related to spell-check, language services, or external network calls.
    Affected if External or third-party spell-check services are configured or enabled in the application settings.
  4. Review application logs for spell-check activity
    Examine log files in the application's log directory (commonly under %PROGRAMDATA%\Acronis\Cyber Files\Logs\) for entries containing keywords such as 'spell', 'SpellCheck', or network requests to external spell services.
    Affected if Logs show outgoing network connections to spell-check servers or contain typed content captured by the spell-check feature.

A user is affected if Acronis Cyber Files for Windows is installed with a version below 9.0 and the spell-check feature is enabled or configured to use external services.

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 9.0 or later
Fixed in 9.0
Interim mitigation

Upgrade Acronis Cyber Files Windows to build 9.0.0x24 or later. As an interim measure, disable third-party spell-checking integrations or network-based spell services within the application if such controls are available.

Recommended fix Moderate confidence

Acronis Cyber Files 9.0 (build 9.0.0x24 or later)

  1. Verify the current installed version of Acronis Cyber Files on the Windows system
  2. Download Acronis Cyber Files version 9.0 or later from the official Acronis download center
  3. Ensure a backup of critical data exists before proceeding with the upgrade
  4. Run the installer with administrative privileges
  5. Follow the on-screen prompts to complete the installation
  6. Verify that the installed build number is 9.0.0x24 or later after upgrade

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

Fix this in Cyber Files Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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