dbcve.org
Backupper WorkstationApplication · Aomeitech

CVE-2025-8612

HIGH · 7.3 CVSS v3.0 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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
AOMEI Backupper Workstation Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of AOMEI Backupper Workstation. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. User interaction on the part of an administrator is needed additionally. The specific flaw exists within the restore functionality. By creating a junction, an attacker can abuse the service to create arbitrary files. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-27059.

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 local privilege escalation vulnerability in AOMEI Backupper Workstation's restore functionality allows an attacker who already has low-privileged code execution to abuse the service via file system junction points to create arbitrary files. By crafting a junction during restore operations, the attacker can cause the service to write files to privileged locations, achieving SYSTEM-level code execution.

MitigationApply vendor-supplied patches when available. Until then, restrict administrator usage of the restore functionality, monitor for unauthorized junction creation in restore paths, and limit which users can execute the backup software.

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
Backupper WorkstationApplication
Affected:= 4.7.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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. Identify AOMEI Backupper Workstation installation
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\AOMEI Backupper for the installed software. Look for 'AOMEI Backupper Workstation' in the program list.
    Affected if The program is installed and no patch has been applied to address this vulnerability.
  2. Determine installed version
    Right-click the AOMEI Backupper Workstation executable or DLL in the installation folder, select Properties, then view the Details tab to find the File Version. Alternatively, run 'wmic product get name,version' or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the installed version.
    Affected if The installed version is 4.7.2, matching the affected version listed for this CVE.
  3. Verify AOMEI Backupper Service presence
    Open Services (services.msc) and look for 'AOMEI Backupper Service' or similar AOMEI service entries. Confirm the service exists and its startup type.
    Affected if The AOMEI Backupper service is installed and runs, providing the restore functionality that can be exploited.
  4. Inspect restore target directories for junction points
    Use 'dir /aL' or PowerShell 'Get-Item -Path <path> -Force | Select-Object LinkType, Target' to list junction points in common restore paths such as C:\, C:\Program Files\, and C:\Windows\. Check if any unexpected junctions exist in these locations.
    Affected if Junction points exist in system restore directories that were not created by legitimate administrators or the backup software itself.
  5. Audit recent file creations in privileged locations
    Use Windows Event Viewer or File Explorer to review recent file creations in C:\Windows\System32\, C:\Program Files\, and other SYSTEM-privileged directories. Look for files created around the time of restore operations by low-privileged users.
    Affected if Files appear in privileged directories that were created by the AOMEI Backupper service on behalf of a low-privileged user session.

You are affected if AOMEI Backupper Workstation version 4.7.2 is installed and the service runs, allowing low-privileged users to trigger restore operations that could be manipulated via junction points to achieve SYSTEM-level file write access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches when available. Until then, restrict administrator usage of the restore functionality, monitor for unauthorized junction creation in restore paths, and limit which users can execute the backup software.

Fix this in Backupper Workstation Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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