CVE-2024-53946
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 LTE AC900 router 1.0.13 is vulnerable to Cross-Site Request Forgery (CSRF) on its web management interface. This vulnerability allows an attacker to trick an authenticated admin user into performing unauthorized actions, such as exploiting a command injection vulnerability in /goform/formMultiApnSetting. Successful exploitation can also lead to unauthorized configuration changes.
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 LTE AC900 router firmware 1.0.13 contains a CSRF vulnerability in its web management interface. An attacker can craft malicious links or pages that, when clicked by an authenticated administrator, cause the browser to perform unintended actions on the router. This CSRF flaw can be chained with a command injection in /goform/formMultiApnSetting, allowing remote command execution or unauthorized configuration changes.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm router model and firmware versionAccess the router's web management interface (typically at 192.168.1.1 or 192.168.0.1) and check the firmware version displayed in the system status or administration page. Alternatively, check the bootloader or upgrade page for version information.Affected if The firmware version is 1.0.13 (the specifically affected version).
-
Verify the web management interface is accessibleAttempt to access the router's HTTP/HTTPS web interface on the local network. Confirm you can reach the login page or an authenticated dashboard.Affected if The web management interface is exposed and accessible on the local network.
-
Check if /goform/formMultiApnSetting endpoint existsNavigate to or inspect the Multi-APN settings page in the router web interface, or attempt a request to /goform/formMultiApnSetting to confirm the endpoint responds.Affected if The /goform/formMultiApnSetting endpoint is present and responds to requests.
-
Inspect form submissions for anti-CSRF tokensSubmit a state-changing form (such as Multi-APN settings, wireless settings, or WAN settings) while capturing the HTTP request. Examine whether the form includes a unique token parameter (such as token, csrf, or auth) that changes per session, or whether the request validates Origin/Referer headers.Affected if Forms lack anti-CSRF tokens and the server does not validate Origin/Referer headers.
A user is affected if they are running KuWFi 4G LTE AC900 firmware version 1.0.13 with the web interface accessible and forms (including /goform/formMultiApnSetting) lacking anti-CSRF token protection.
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 dataImplement anti-CSRF tokens on all state-changing forms in the web interface, validate Origin/Referer headers, and apply SameSite cookie attributes. If available, update to a patched firmware version.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53946 — 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-53946 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