CVE-2025-3759
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 · uneditedEndpoint /cgi-bin-igd/netcore_set.cgi which is used for changing device configuration is accessible without authentication. This poses a significant security threat allowing for e.g: administrator account hijacking or AP password changing. 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 · high confidenceA critical authentication bypass vulnerability exists in the /cgi-bin-igd/netcore_set.cgi endpoint of certain network devices (likely routers or access points). This CGI script, which handles device configuration changes, is accessible without any authentication, allowing remote attackers to hijack administrator accounts or modify Access Point passwords. The lack of authentication combined with the privileged nature of the affected function results in severe impact.
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 the vulnerable endpoint exists on the deviceAccess the device's web interface or use a tool like curl to request GET /cgi-bin-igd/netcore_set.cgi and check for a valid response or error message rather than a 404 Not FoundAffected if The endpoint responds with any status code other than 404 (indicating the CGI script is present)
-
Test authentication requirement for the endpointSend an unauthenticated HTTP request (no cookies, no Authorization header) to /cgi-bin-igd/netcore_set.cgi and examine whether the device returns configuration data or accepts commands instead of redirecting to a login pageAffected if The endpoint returns configuration data, accepts commands, or does not require authentication (no login redirect)
-
Verify network accessibility of the CGI endpointFrom an untrusted network segment (or externally), attempt to reach the device's IP on port 80/443 and request /cgi-bin-igd/netcore_set.cgi to determine if the endpoint is exposed beyond the local management networkAffected if The endpoint is reachable from untrusted networks or the internet rather than only from a trusted management VLAN
The device is affected if the /cgi-bin-igd/netcore_set.cgi endpoint exists and is accessible without authentication, especially if reachable from untrusted networks.
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 dataSince the vendor did not respond to disclosure, organizations should immediately restrict network access to the affected endpoint using firewall rules or network segmentation, ideally placing the device in a isolated VLAN with no external exposure. If the device cannot be patched, consider replacement with a vendor that provides timely security updates.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3759 — 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-3759 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