CVE-2026-36539
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 · uneditedNetis AC1200 Router NC21 V4.0.1.4296 exposes a CGI endpoint /cgi-bin/skk_get.cgi that returns the entire router configuration as a JSON response with no authentication required. Any attacker on the LAN can send a single HTTP GET request and instantly retrieve administrator credentials, WiFi passwords, PPPoE credentials, DDNS credentials, and a full map of all connected devices.
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 confidenceThe Netis AC1200 Router NC21 V4.0.1.4296 contains an unauthenticated information disclosure vulnerability in the CGI endpoint /cgi-bin/skk_get.cgi. This endpoint returns the complete router configuration as JSON without requiring any authentication, allowing any attacker on the LAN to retrieve sensitive credentials including administrator usernames/passwords, WiFi keys, PPPoE credentials, DDNS credentials, and a full listing of connected devices via a single HTTP GET request.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify Netis router modelCheck the device label or access the router admin panel to confirm the model is Netis AC1200 Router NC21Affected if Device is a Netis AC1200 Router NC21
-
Check firmware versionAccess router admin panel (typically at 192.168.1.1) and look for firmware version in System or Administration settings, or check via telnet/SSH if enabledAffected if Firmware version matches V4.0.1.4296 or is an earlier unreleased version
-
Test vulnerable CGI endpoint accessibilitySend an HTTP GET request to http://<router-ip>/cgi-bin/skk_get.cgi from a device on the LAN, without providing any authentication headers or credentialsAffected if The endpoint responds with HTTP 200 and returns JSON data without requiring authentication
-
Verify sensitive data exposureExamine the JSON response from /cgi-bin/skj_get.cgi for fields containing passwords, keys, or credential-related keywords (e.g., 'password', 'key', 'pppoe', 'ddns', 'admin')Affected if Response contains administrator credentials, WiFi keys, PPPoE credentials, DDNS credentials, or connected device information without authentication
A user is affected if they have a Netis AC1200 Router NC21 running firmware V4.0.1.4296 and the /cgi-bin/skk_get.cgi endpoint returns sensitive configuration data without requiring 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 dataApply vendor firmware patch when available; if no patch exists, disable remote management, implement network segmentation to restrict LAN access to trusted devices only, and consider replacing the affected device.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36539 — 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-2026-36539 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