dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-12003

HIGH · 8.2 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 →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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 path traversal vulnerability has been identified in WebDAV, which may allow unauthenticated remote attackers to impact the integrity of the device. Refer to the ' Security Update for ASUS Router Firmware' 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 · moderate confidence

A path traversal vulnerability in the WebDAV component of ASUS router firmware allows unauthenticated remote attackers to access files outside the intended directory through specially crafted requests, potentially enabling modification of system files and impacting device integrity.

MitigationApply the latest ASUS router firmware update from the official ASUS Security Advisory; if the patch is not yet available, consider disabling the WebDAV service or implementing network access controls to limit exposure until the update is released.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/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. Identify the ASUS router model
    Locate the model number on the device label (usually on the bottom or back of the router) or in the admin interface under Device Information
    Affected if The device is an ASUS router with WebDAV capability
  2. Check the installed firmware version
    Log into the router admin interface (typically at 192.168.1.1), navigate to Administration > Firmware Upgrade or System Settings, and record the current firmware version number
    Affected if The firmware version is older than the patched version released in the ASUS security advisory for CVE-2025-12003
  3. Verify if WebDAV service is enabled
    In the router admin interface, look for USB-related or storage settings (such as USB Application > FTP/SMB Server or Cloud Disk settings), and check whether WebDAV or Cloud Disk feature is turned on
    Affected if WebDAV or Cloud Disk functionality is enabled on the router
  4. Confirm WebDAV port accessibility
    Check if the router has port 8080 or 443 open for WebDAV access (check in Administration > System > Port Forwarding or use an external port scanner from outside the local network)
    Affected if WebDAV is enabled and accessible

You are affected if you have an ASUS router with WebDAV enabled and your firmware version predates the ASUS security patch for CVE-2025-12003.

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 latest ASUS router firmware update from the official ASUS Security Advisory; if the patch is not yet available, consider disabling the WebDAV service or implementing network access controls to limit exposure until the update is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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