# CVE-2025-10957: Unrestricted FTP Access Vulnerability in Syrotech Router

> Remote attackers can access sensitive configuration and credentials on Syrotech GPON routers by using default FTP credentials.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 25 Sep 2025
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-3vcj-cj9g-vfr3

## What is CVE-2025-10957?

CVE-2025-10957 is a high-severity vulnerability in Syrotech SY-GPON-2010-WADONT, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This vulnerability exists in the Syrotech SY-GPON-2010-WADONT router due to improper access control in its FTP service. A remote attacker could exploit this vulnerability by establishing an FTP connection using default credentials, potentially gaining unauthorized access to configuration files, user credentials, or other sensitive information stored on the targeted device.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-10957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10957 is a high-severity vulnerability in Syrotech SY-GPON-2010-WADONT, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10957 in the wild and no public exploit code.

Affected product: Syrotech SY-GPON-2010-WADONT. 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-10957/ (Markdown: https://insights.sbomify.com/CVE-2025-10957/index.md)
```

## Sources

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

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