CVE-2025-43984
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 was discovered on KuWFi GC111 devices (Hardware Version: CPE-LM321_V3.2, Software Version: GC111-GL-LM321_V3.0_20191211). They are vulnerable to unauthenticated /goform/goform_set_cmd_process requests. A crafted POST request, using the SSID parameter, allows remote attackers to execute arbitrary OS commands with root privileges.
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 confidenceKuWFi GC111 devices with firmware GC111-GL-LM321_V3.0_20191211 contain an unauthenticated command injection vulnerability in the /goform/goform_set_cmd_process web endpoint. Attackers can inject arbitrary OS commands via the SSID parameter in POST requests, achieving root-level command execution without any authentication.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the device modelAccess the device's web管理界面 or check the device label/marketing material to confirm it is a KuWFi GC111 deviceAffected if The device is a KuWFi GC111 unit
-
Check the firmware versionLog into the device's web管理界面 and navigate to the status or system information page to view the installed firmware version; compare it to the affected version GC111-GL-LM321_V3.0_20191211 or earlierAffected if The firmware version is GC111-GL-LM321_V3.0_20191211 or any earlier version of this firmware line
-
Verify the web管理界面 is network-accessibleAttempt to access the device's IP address on ports 80 or 443 from a remote system to confirm the web interface is reachable; check router or firewall rules for port 80/443 inbound accessAffected if The device's web management interface is accessible from an untrusted network segment or the internet
-
Confirm the vulnerable endpoint respondsSend a POST request to /goform/goform_set_cmd_process (or /goform/goform_set_cmd_process) with a minimal SSID parameter; if the device responds, the endpoint exists and may be exploitableAffected if The /goform/goform_set_cmd_process endpoint accepts requests and returns a response without requiring authentication
You are affected if you have a KuWFi GC111 device running firmware GC111-GL-LM321_V3.0_20191211 or earlier, and the device's web管理界面 is network-accessible from an untrusted network.
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 dataRestrict network access to the device's management interface to prevent external attackers from reaching it; if remote management is not required, disable it entirely. Consider network segmentation or device replacement if the vendor does not provide a firmware patch.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43984 — 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-2025-43984 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