CVE-2024-51228
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 · uneditedAn issue in TOTOLINK-CX-A3002RU V1.0.4-B20171106.1512 and TOTOLINK-CX-N150RT V2.1.6-B20171121.1002 and TOTOLINK-CX-N300RT V2.1.6-B20170724.1420 and TOTOLINK-CX-N300RT V2.1.8-B20171113.1408 and TOTOLINK-CX-N300RT V2.1.8-B20191010.1107 and TOTOLINK-CX-N302RE V2.0.2-B20170511.1523 allows a remote attacker to execute arbitrary code via the /boafrm/formSysCmd component.
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 confidenceCommand injection vulnerability in TOTOLINK router web interface. The /boafrm/formSysCmd endpoint allows remote attackers to execute arbitrary system commands without proper input sanitization, likely through the system command execution functionality in the router's firmware.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the device is a TOTOLINK routerAccess the web management interface (usually http://192.168.0.1 or similar) and check the login page footer, HTML source, or response headers for 'TOTOLINK' branding. Alternatively, use nmap or curl to probe the HTTP service and inspect server banners or HTML content for TOTOLINK identifiers.Affected if The device displays TOTOLINK branding or returns TOTOLINK-specific HTTP responses.
-
Confirm web interface is remotely accessibleDetermine if the router web interface is reachable from outside the local network. Check router port forwarding rules, firewall configurations, or test remote IP connectivity to ports 80/443. Use 'curl -I <external-ip>:80' or 'nc -zv <ip> 80 443' to test accessibility.Affected if The HTTP/HTTPS ports (80/443) are open and respond to external/remote requests.
-
Check for the vulnerable formSysCmd endpointSend an HTTP GET or POST request to '/boafrm/formSysCmd' on the router's IP address. For example: 'curl -X POST http://<router-ip>/boafrm/formSysCmd' or check if the URL returns a valid response rather than a 404 error.Affected if The endpoint exists and responds (even with an error), indicating the command execution functionality is present.
-
Inspect firmware version if accessibleNavigate to the router's admin panel System Status or Firmware Upgrade page to find the firmware version. Alternatively, check the HTTP response headers or the footer of the web interface for version strings. If CLI access is available, run 'cat /proc/version' or 'uname -a' if telnet/SSH is enabled.Affected if The firmware version matches any known TOTOLINK versions that contain this vulnerability (compare against vendor security advisories).
You are affected if you have a TOTOLINK router with its web interface remotely accessible and the /boafrm/formSysCmd endpoint is present and responsive.
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 patches when available. If no patch exists, consider network isolation or replacement of affected devices. Disable remote management interfaces if not required.
- Consultation8.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51228 — 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-51228 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