CVE-2024-5786
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 · uneditedCross-Site Request Forgery vulnerability in Comtrend router WLD71-T1_v2.0.201820, affecting the GRG-4280us version. This vulnerability allows an attacker to force an end user to execute unwanted actions in a web application to which he is authenticated.
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 confidenceCross-Site Request Forgery vulnerability in Comtrend WLD71-T1_v2.0.201820 and GRG-4280us routers allows authenticated users to be tricked into executing unintended web application actions. An attacker crafts malicious requests that the victim's browser automatically sends to the router's web interface, exploiting the lack of proper CSRF token validation.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 router modelLocate the physical router and check the model label, or log into the web admin interface and look for the model name on the status or device info page.Affected if Router is not a Comtrend WLD71-T1_v2.0.201820 or GRG-4280us model.
-
Check firmware versionIn the router web admin interface, navigate to the status or system settings page and locate the firmware version field. Compare it against the affected version: WLD71-T1_v2.0.201820 and GRG-4280us.Affected if Firmware version matches exactly WLD71-T1_v2.0.201820 or GRG-4280us.
-
Verify web management interface is enabledAccess the router admin panel via browser at the default gateway IP (commonly 192.168.1.1). Check if the login page loads, indicating the HTTP/HTTPS web interface is active.Affected if Web interface is accessible and accepts authentication.
-
Confirm session handling methodLog into the router admin panel and inspect the HTML forms used for configuration changes. Look for hidden input fields containing CSRF tokens or anti-CSRF tokens in the request headers.Affected if Configuration forms lack CSRF token fields and the router does not validate anti-CSRF tokens on POST requests.
A user is affected if they own a Comtrend WLD71-T1_v2.0.201820 or GRG-4280us router with the specified firmware and have the web management interface enabled without proper CSRF protection in place.
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 update if available; otherwise implement anti-CSRF token validation in the router's web interface or use SameSite cookie attributes to mitigate session hijacking attempts.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5786 — 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-5786 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