# CVE-2025-59372: Path traversal in Router

> Authenticated attackers can write files outside intended directories on ASUS routers, compromising device integrity.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2025
- **Updated:** 25 Nov 2025
- **Also known as:** GHSA-5c6f-f3p9-5w4q

## What is CVE-2025-59372?

CVE-2025-59372 is a medium-severity path traversal vulnerability in ASUS Router, published on 25 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-59372?


## How do I fix CVE-2025-59372?

No fix has been published for CVE-2025-59372 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59372 being exploited?

There is no known exploitation of CVE-2025-59372 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59372 and fix it if it is affected.

What it is: CVE-2025-59372 is a medium-severity path traversal vulnerability in ASUS Router, published on 25 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59372 in the wild and no public exploit code.

Affected product: ASUS Router. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59372/ (Markdown: https://insights.sbomify.com/CVE-2025-59372/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59372
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59372
- OSV: https://osv.dev/vulnerability/CVE-2025-59372

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59372/
Summaries are generated and may contain mistakes; the official description above is the record.