dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-5785

HIGH · 8.0 CVSS v3.1 Published 2024-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
Command injection vulnerability in Comtrend router WLD71-T1_v2.0.201820, affecting the GRG-4280us version. This vulnerability could allow an authenticated user to execute commands inside the router by making a POST request to the URL “/boaform/admin/formUserTracert”.

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 confidence

Command injection vulnerability in Comtrend router WLD71-T1_v2.0.201820 and GRG-4280us web interface. An authenticated attacker can send a crafted POST request to /boaform/admin/formUserTracert to execute arbitrary operating system commands on the router with the device's privilege level.

MitigationRestrict access to the router's administrative interface to trusted networks only, disable remote administration if exposed to the internet, and monitor for unauthorized access attempts. Contact Comtrend for firmware updates; if unavailable, consider network segmentation or hardware replacement.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the router label or access the web interface and look for the model number (WLD71-T1 or GRG-4280us) in the status or admin section
    Affected if The device is a Comtrend WLD71-T1 or GRG-4280us router
  2. Check the firmware version
    Access the router web interface admin panel and navigate to the firmware version or status page; alternatively, check the label on the device itself
    Affected if The firmware version matches or is prior to v2.0.201820 (for WLD71-T1) or the listed version for GRG-4280us
  3. Verify web interface accessibility
    Attempt to access the router web interface on the default IP (typically 192.168.1.1) via HTTP
    Affected if The administrative web interface is reachable on the network
  4. Confirm the vulnerable endpoint exists
    Send a GET request to /boaform/admin/formUserTracert or inspect the router's web page source for this form action
    Affected if The formUserTracert endpoint is present in the web interface
  5. Check for remote administration exposure
    Determine if the router web interface is accessible from outside the local network by testing access via public IP or reviewing port forwarding rules
    Affected if Remote administration (port 80/443) is forwarded or enabled on WAN

You are affected if you have a Comtrend WLD71-T1 or GRG-4280us router running firmware at or below the affected version and the administrative web interface is accessible on your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the router's administrative interface to trusted networks only, disable remote administration if exposed to the internet, and monitor for unauthorized access attempts. Contact Comtrend for firmware updates; if unavailable, consider network segmentation or hardware replacement.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5785 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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