dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-59373

HIGH · 8.5 CVSS v4.0 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
A local privilege escalation vulnerability exists in the restore mechanism of ASUS System Control Interface. It can be triggered when an unprivileged actor copies files without proper validation into protected system paths, potentially leading to arbitrary files being executed as SYSTEM. For more information, please refer to section Security Update for MyASUS in the ASUS Security Advisory.

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

A local privilege escalation vulnerability exists in the restore mechanism of ASUS System Control Interface (MyASUS). An unprivileged actor can copy files without proper validation into protected system paths, enabling arbitrary code execution with SYSTEM privileges.

MitigationApply the vendor security patch from the ASUS Security Advisory for MyASUS when released. Until patched, restrict write access to the protected system paths used by the restore mechanism.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm ASUS System Control Interface installation
    Check for ASUS System Control Interface (ASCI) or related services. On Windows, open Programs and Features or run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*ASUS*System*Control*'}. Also check for ASUS service processes in Task Manager or via: Get-Service | Where-Object {$_.DisplayName -like '*ASUS*'}.
    Affected if ASUS System Control Interface is installed on the system.
  2. Identify the restore mechanism component
    Look for ASUS restore or backup-related services and executables. Check for processes or services containing keywords like 'ASUS', 'restore', 'recovery', or 'System Control' in their names. Inspect the installation directory (typically C:\Program Files\ASUS\ or C:\Program Files (x86)\ASUS\) for restore-related executables or modules.
    Affected if ASUS restore functionality components are present on the system.
  3. Verify restore service configuration
    Examine the ASUS restore service status. Run: Get-Service | Where-Object {$_.Name -like '*ASUS*Restore*' -or $_.Name -like '*ASUS*Recovery*'}. Also check for scheduled tasks related to ASUS restore: Get-ScheduledTask | Where-Object {$_.TaskName -like '*ASUS*Restore*' -or $_.TaskName -like '*ASUS*Recovery*'}.
    Affected if The ASUS restore service or scheduled task is present and enabled.
  4. Inspect restore feature permissions
    Review file system permissions on ASUS restore directories and executables. Check if non-privileged users have write access to restore destination paths (typically protected system directories). Use: Get-Acl 'C:\Program Files\ASUS\*' -ErrorAction SilentlyContinue | Select-Object Path, AccessToString.
    Affected if Non-administrative users have write access to restore destination directories or the restore feature permits unprivileged file operations.

A system is likely affected if ASUS System Control Interface with restore functionality is installed and the restore mechanism allows unprivileged users to write files to protected system paths without proper validation.

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 the vendor security patch from the ASUS Security Advisory for MyASUS when released. Until patched, restrict write access to the protected system paths used by the restore mechanism.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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