Missing AuthorizationWeakness · CWE-862

CVE-2025-13348

HIGH · 8.5 CVSS v4.0 Published 2026-02-02
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
An improper access control vulnerability exists in ASUS Secure Delete Driver of ASUS Business Manager. This vulnerability can be triggered by a local user sending a specially crafted request, potentially leading to the creation of arbitrary files in a specified path. Refer to the "Security Update for ASUS Business Manager" section on the ASUS Security Advisory for more information.

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

This is an improper access control vulnerability in the ASUS Secure Delete Driver component of ASUS Business Manager. A local authenticated user can send specially crafted requests to the driver to create arbitrary files in specified paths, potentially leading to privilege escalation or denial of service.

MitigationApply the vendor patch from ASUS Security Advisory for Business Manager. If the software is not required, uninstall ASUS Business Manager to eliminate the attack surface.

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. Check if ASUS Business Manager is installed
    Look for ASUS Business Manager in the list of installed programs via Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell and filter for 'ASUS Business Manager'
    Affected if ASUS Business Manager is present on the system
  2. Locate the ASUS Secure Delete Driver file
    Search for driver files associated with ASUS Secure Delete - typical file names include asusdel.sys, asusdeletesys, or similar in C:\Windows\System32\drivers\ or the ASUS Business Manager installation directory
    Affected if The ASUS Secure Delete Driver file (asusdel*.sys) exists on the system
  3. Verify if the driver service is present and running
    Open Services (services.msc) and look for a service related to ASUS Secure Delete, or run 'sc query' in Command Prompt to enumerate services containing 'ASUS' or 'Delete'
    Affected if A service associated with the ASUS Secure Delete Driver is registered and running
  4. Check the installed version of ASUS Business Manager
    Right-click on ASUS Business Manager in Programs and Features to view the version, or check the version property of the main executable in the installation folder (typically in C:\Program Files\ASUS\ASUS Business Manager\)
    Affected if The installed version matches or falls within any affected version range provided by ASUS Security Advisory (if available)
  5. Confirm authenticated user context exposure
    Review system access logs or audit policies to determine if untrusted local user accounts exist on the system, as the vulnerability requires a local authenticated user to send requests to the driver
    Affected if Non-administrative or untrusted local user accounts have access to the system where the vulnerable driver is present

The system is affected if ASUS Business Manager with the ASUS Secure Delete Driver is installed and running, allowing a local authenticated user to exploit improper access controls in the driver.

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 patch from ASUS Security Advisory for Business Manager. If the software is not required, uninstall ASUS Business Manager to eliminate the attack surface.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13348 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