dbcve.org
Hyper Backup ExplorerApplication · Synology

CVE-2022-49042

HIGH · 7.8 CVSS v3.1 Published 2026-06-03
Fix available
A fix is available. Upgrade to 3.0.1-0156 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
An inclusion of functionality from untrusted control sphere vulnerability in MinGW DLL component in Synology Hyper Backup Explorer before 3.0.1-0156 allows local users to execute arbitrary code via unspecified vectors.

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

Synology Hyper Backup Explorer before version 3.0.1-0151 contains a DLL hijacking vulnerability in its MinGW DLL component. The application loads DLLs from an untrusted control sphere (likely without secure path resolution), allowing a local attacker to place a malicious DLL in a search path location that the application will load, resulting in arbitrary code execution with the application's privileges.

MitigationUpgrade Synology Hyper Backup Explorer to version 3.0.1-0156 or later. Until upgraded, monitor the application directory for unauthorized DLL files and ensure only trusted administrators have write access to application directories.

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
Hyper Backup ExplorerApplication
Affected:< 3.0.1-0156

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check if Synology Hyper Backup Explorer is installed
    Look for the application in typical installation directories such as C:\Program Files\Synology\Hyper Backup Explorer, or search for the executable file named HyperBackupExplorer.exe using File Explorer or the command: dir /s /b C:\*HyperBackupExplorer.exe
    Affected if The application is not found on the system, then this CVE does not apply
  2. Determine the installed version
    Right-click on HyperBackupExplorer.exe, select Properties, and view the Details tab to find the File Version or Product Version
    Affected if The version number displayed is less than 3.0.1-0156 (for example, 3.0.0-xxxx or any earlier version)
  3. Check application directory write permissions
    Right-click on the folder containing HyperBackupExplorer.exe, select Properties, go to the Security tab, and review the permissions for Users or other non-admin groups. Alternatively, run: icacls "C:\Program Files\Synology\Hyper Backup Explorer"
    Affected if Users or Authenticated Users have Write or Modify permissions to the application directory, allowing them to place a malicious DLL
  4. Check working directory write permissions
    Identify the directory from which the application is launched. Right-click on that folder, select Properties, go to the Security tab, and verify write permissions for non-admin users. If launching from a user-writable folder like Downloads or Desktop, this increases exploitability
    Affected if The working directory is writable by standard users, allowing them to place a malicious DLL that gets loaded by the application

The system is affected if Synology Hyper Backup Explorer version is below 3.0.1-0156 AND either the application directory or the working directory is writable by non-admin users, enabling DLL hijacking.

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

Upgrade Synology Hyper Backup Explorer to version 3.0.1-0156 or later. Until upgraded, monitor the application directory for unauthorized DLL files and ensure only trusted administrators have write access to application directories.

Recommended fix High confidence

3.0.1-0156 or later

  1. Open Synology DiskStation Manager (DSM) and navigate to Package Center
  2. Locate Synology Hyper Backup Explorer in the installed packages
  3. Click on the package and select 'Update' to install the latest available version
  4. Alternatively, download Hyper Backup Explorer version 3.0.1-0156 or later directly from the Synology Download Center at https://www.synology.com/en-global/support/download
  5. Install the downloaded package via Package Center or manually via the .spk file
  6. Verify the installed version is 3.0.1-0156 or higher by checking Help > About in Hyper Backup Explorer

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

Fix this in Hyper Backup Explorer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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