CVE-2024-31816
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 · uneditedIn TOTOLINK EX200 V4.0.3c.7646_B20201211, an attacker can obtain sensitive information without authorization through the function getEasyWizardCfg.
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 TOTOLINK EX200 V4.0.3c.7646_B20201211 router firmware contains an information disclosure vulnerability in the getEasyWizardCfg function. This function improperly exposes sensitive configuration data without requiring authentication, allowing an unauthenticated remote attacker to retrieve potentially confidential information such as network credentials, administrative settings, or device configuration details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.0.3c.7646_b20201211CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the device modelAccess the router's web interface or check the device label to confirm the model is TOTOLINK EX200Affected if The device is a TOTOLINK EX200 router
-
Check the installed firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the firmware version, or use the command 'cat /proc/version' or 'cat /etc/version' if you have shell accessAffected if The firmware version is exactly 4.0.3c.7646_b20201211
-
Test for the vulnerable endpointSend an HTTP GET request to the router's IP address targeting the getEasyWizardCfg function, typically at a path like '/cgi-bin/luci/api/xxx' or similar endpoint that invokes this function - no authentication headers should be includedAffected if The request returns sensitive configuration data (network credentials, admin settings, or device configuration) without requiring any authentication
-
Verify authentication is not enforcedRepeat the request from step 3 without providing any session cookies, tokens, or Basic Auth credentialsAffected if The vulnerable function returns configuration data to an unauthenticated request
A user is affected if they have a TOTOLINK EX200 router running firmware version 4.0.3c.7646_b20201211 and the getEasyWizardCfg endpoint is accessible without 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-supplied firmware update when available; until then, restrict network access to the device's management interface and monitor for unauthorized access attempts.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31816 — 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-2024-31816 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