# CVE-2025-61941: Path traversal in WXR9300BE6P series

> Administrative users can exploit path traversal to alter files and execute arbitrary OS commands on BUFFALO WXR9300BE6P routers.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/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:** 15 Oct 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-6q6j-vx5c-rh5j

## What is CVE-2025-61941?

CVE-2025-61941 is a high-severity path traversal vulnerability in BUFFALO INC. WXR9300BE6P series, published on 15 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A path traversal issue exists in WXR9300BE6P series firmware versions prior to Ver.1.10. Arbitrary file may be altered by an administrative user who logs in to the affected product. Moreover, arbitrary OS command may be executed via some file alteration.

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

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


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

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

## Is CVE-2025-61941 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61941 is a high-severity path traversal vulnerability in BUFFALO INC. WXR9300BE6P series, published on 15 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61941 in the wild and no public exploit code.

Affected product: BUFFALO INC. WXR9300BE6P series. 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-61941/ (Markdown: https://insights.sbomify.com/CVE-2025-61941/index.md)
```

## Sources

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

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