Path TraversalWeakness · CWE-22

CVE-2025-59372

MEDIUM · 6.9 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 →
75/100
Remediation priority · High
Remotely reachable 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 certain router models. A remote, authenticated attacker could exploit this vulnerability to write files outside the intended directory, potentially affecting device integrity. 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

This is a path traversal vulnerability in ASUS router firmware allowing authenticated remote attackers to write files outside the intended directory. The ability to write files to arbitrary locations on the device can compromise system integrity and potentially enable further exploitation.

MitigationApply the firmware update from the ASUS Security Advisory for affected router models. Restrict administrative access to trusted IP addresses and disable remote management if not required.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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 ASUS router model and firmware version
    Log into the router admin web interface (typically at 192.168.1.1) and navigate to Administration > Firmware Upgrade or General > System to view the exact model number and current firmware version. Alternatively, check the label on the router device itself for the model.
    Affected if The router is an ASUS model running firmware for which CVE-2025-59372 has not been patched. Compare your firmware version to the affected versions listed in the ASUS Security Advisory.
  2. Confirm remote management or VPN feature status
    In the router admin interface, go to WAN > Remote Management (or External Access > Enable Web GUI from WAN) and check if remote access is enabled. Also check VPN > VPN Server settings if VPN remote access is configured.
    Affected if Remote management (Web GUI from WAN) or VPN remote access is enabled, allowing authenticated attackers to reach the vulnerable service from external networks.
  3. Verify administrative access control settings
    In the router admin interface, navigate to Firewall > General or Administration > System to review allowed IP addresses for administrative access. Check if access is restricted to specific trusted IP addresses or if it accepts connections from any source.
    Affected if Administrative interface accepts connections from untrusted networks or IP addresses without restriction, enabling remote authenticated attackers to exploit the path traversal flaw.

You are affected if your ASUS router model is listed in the CVE-2025-59372 advisory and is running a vulnerable firmware version with remote management or VPN access enabled that allows unauthenticated or weakly authenticated attackers to reach the router admin interface.

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 firmware update from the ASUS Security Advisory for affected router models. Restrict administrative access to trusted IP addresses and disable remote management if not required.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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