CVE-2024-53945
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 · uneditedThe KuWFi 4G AC900 LTE router 1.0.13 is vulnerable to command injection on the HTTP API endpoints /goform/formMultiApnSetting and /goform/atCmd. An authenticated attacker can execute arbitrary OS commands with root privileges via shell metacharacters in parameters such as pincode and cmds. Exploitation can lead to full system compromise, including enabling remote access (e.g., enabling telnet).
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 KuWFi 4G AC900 LTE router firmware 1.0.13 contains OS command injection vulnerabilities in the /goform/formMultiApnSetting and /goform/atCmd API endpoints. Authenticated attackers can inject shell metacharacters into parameters such as pincode and cmds, allowing arbitrary OS command execution with root privileges. This enables full device compromise including activation of services like telnet for persistent remote access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLocate the router label or access the web admin interface to confirm the device is a KuWFi 4G AC900 LTE routerAffected if The device is not a KuWFi 4G AC900 LTE router, then it is not affected by this specific CVE
-
Check firmware versionAccess the router web admin interface and navigate to the firmware or system information page to determine the installed firmware versionAffected if The firmware version is 1.0.13, the device is running the affected version
-
Verify affected HTTP API endpoints existAttempt to access or probe the endpoints /goform/formMultiApnSetting and /goform/atCmd on the router's web interfaceAffected if These endpoints return valid HTTP responses, indicating the vulnerable API is present
-
Check for unauthorized servicesUse network scanning or check router process list for unexpected services such as telnet, reverse shells, or unfamiliar listening portsAffected if Unexpected services like telnet on port 23 or other remote access services are running, this may indicate the vulnerability has been exploited
-
Determine web interface accessibilityCheck if the router web admin interface is accessible from the WAN (internet-facing) side, or review firewall rules and port forwarding settingsAffected if The web management interface is exposed to the internet, increasing the attack surface for this vulnerability
If the device is a KuWFi 4G AC900 LTE router running firmware version 1.0.13 with the web management interface accessible, it is likely affected by this authenticated command injection vulnerability.
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; until then, disable remote management interfaces, restrict administrative access to trusted IP addresses only, and monitor for unauthorized changes or new services like telnet.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53945 — 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-53945 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