# CVE-2025-14910: Edimax BR-6208AC FTP Daemon Service handle_retr path traversal

> Remote attackers can exploit a path traversal flaw in the FTP daemon to read arbitrary files on discontinued Edimax routers.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-x3hm-53cx-8hp8

## What is CVE-2025-14910?

CVE-2025-14910 is a medium-severity path traversal vulnerability in Edimax BR-6208AC, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in Edimax BR-6208AC 1.02. This impacts the function handle_retr of the component FTP Daemon Service. The manipulation results in path traversal. The attack may be launched remotely. The exploit is now public and may be used. Edimax confirms this issue: "This product is no longer available in the market and has been discontinued for five years. Consequently, Edimax no longer provides technical support, firmware updates, or security patches for this specific model. However, to ensure the safety of our remaining active users, we acknowledge this report and will take the following mitigation actions: (A) We will issue an official security advisory on our support website. (B) We will strongly advise users to disable the FTP service on this device to mitigate the reported risk, by which the product will still work for common use. (C) We will recommend users upgrade to newer, supported models." This vulnerability only affects products that are no longer supported by the maintainer.

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

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

It affects 1 product.


Products: Edimax Br-6208ac Firmware.

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

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

## Is CVE-2025-14910 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14910 exists.

## Other vulnerabilities in Edimax BR-6208AC

- [CVE-2025-70161](https://insights.sbomify.com/CVE-2025-70161/): Command injection in n/a (critical 9.8)
- [CVE-2026-1972](https://insights.sbomify.com/CVE-2026-1972/): Edimax BR-6208AC auth_check_userpass2 default credentials (medium 6.9)
- [CVE-2025-15256](https://insights.sbomify.com/CVE-2025-15256/): Edimax BR-6208AC Web-based Configuration formStaDrvSetup command injection (medium 6.9)
- [CVE-2025-15257](https://insights.sbomify.com/CVE-2025-15257/): Edimax BR-6208AC Web-based Configuration formRoute command injection (medium 6.9)
- [CVE-2025-15258](https://insights.sbomify.com/CVE-2025-15258/): Edimax BR-6208AC Web-based Configuration formALGSetup redirect (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14910 is a medium-severity path traversal vulnerability in Edimax BR-6208AC, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14910 exists.

Affected product: Edimax BR-6208AC. 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-14910/ (Markdown: https://insights.sbomify.com/CVE-2025-14910/index.md)
```

## Sources

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

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