# CVE-2025-3758: Exposure of Device Configuration without Authentication in WF2220

> Unauthenticated attackers can access a specific endpoint to retrieve device configuration, including cleartext passwords, on Netis WF2220 devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-q5pr-32h7-qgvw

## What is CVE-2025-3758?

CVE-2025-3758 is a high-severity vulnerability in Netis Systems WF2220, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WF2220 exposes endpoint /cgi-bin-igd/netcore_get.cgi that returns configuration of the device to unauthorized users. Returned configuration includes cleartext password.
The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2025-3758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3758 is a high-severity vulnerability in Netis Systems WF2220, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3758 in the wild and no public exploit code.

Affected product: Netis Systems WF2220. 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-3758/ (Markdown: https://insights.sbomify.com/CVE-2025-3758/index.md)
```

## Sources

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

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