CVE-2025-3758
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWF2220 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe WF2220 network device exposes a configuration endpoint at /cgi-bin-igd/netcore_get.cgi that can be accessed by unauthorized users without authentication. The endpoint returns the device's full configuration including cleartext passwords, allowing attackers to obtain administrative credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is WF2220Access the device administrative interface or check the device label/marketing materials to verify the model number is WF2220Affected if Device model is WF2220 and the vulnerable firmware version is running
-
Verify the CGI endpoint existsAttempt to access http://<device_ip>/cgi-bin-igd/netcore_get.cgi using curl or a browser without providing any authentication credentialsAffected if The endpoint responds with any HTTP status code (200, 404, 500, etc.) indicating the CGI script exists on the device
-
Check for unauthenticated config disclosureSend a request to the netcore_get.cgi endpoint without any session cookies or authentication headers and examine the response for configuration dataAffected if The endpoint returns device configuration data (such as network settings, admin credentials, or other sensitive parameters) without requiring any login or authentication token
-
Verify cleartext password exposureSearch the response from the netcore_get.cgi endpoint for password fields or credentials transmitted in cleartextAffected if The response contains cleartext passwords, plaintext credentials, or sensitive authentication tokens that should not be exposed
-
Confirm network accessibility of the endpointDetermine if the device management interface (port 80/443 or the CGI endpoint) is exposed to untrusted networks rather than only being accessible from a trusted management VLANAffected if The vulnerable endpoint is reachable from network segments that include untrusted or external attackers
The device is affected if it is a WF2220 model and the /cgi-bin-igd/netcore_get.cgi endpoint returns configuration data including cleartext passwords without requiring any authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict access to the vulnerable endpoint via authentication or network segmentation, and ensure passwords are stored hashed rather than in cleartext. If available, apply vendor firmware updates; otherwise, consider network isolation or replacement of the device.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3758 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data