Missing AuthenticationWeakness · CWE-306

CVE-2025-43983

CRITICAL · 9.1 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
KuWFi CPF908-CP5 WEB5.0_LCD_20210125 devices have multiple unauthenticated access control vulnerabilities within goform/goform_set_cmd_process and goform/goform_get_cmd_process. These allow an unauthenticated attacker to retrieve sensitive information (including the device admin username and password), modify critical device settings, and send arbitrary SMS messages.

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

Multiple unauthenticated access control vulnerabilities in KuWFi CPF908-CP5 devices (firmware WEB5.0_LCD_20210125) allow attackers to access goform/goform_set_cmd_process and goform/goform_get_cmd_process endpoints without authentication, enabling retrieval of admin credentials, modification of device settings, and transmission of arbitrary SMS messages.

MitigationApply vendor firmware patch when available; until then, isolate affected devices behind firewalls or restrict network access to the web management interface to prevent unauthenticated attacks.

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
None

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

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 device model
    Access the device's web management interface or check the device label/metadata for model number CPF908-CP5 or KuWFi brand
    Affected if Device is a KuWFi CPF908-CP5 model
  2. Check firmware version
    Log into the web interface and navigate to System Settings, Status, or About page to view the firmware version string
    Affected if Firmware version matches or predates WEB5.0_LCD_20210125
  3. Test unauthenticated access to get_cmd_process endpoint
    Send an HTTP GET request to http://[device-ip]/goform/goform_get_cmd_process without any authentication headers or session cookies
    Affected if Request returns a valid response containing device configuration data, admin credentials, or SMS settings without being rejected
  4. Test unauthenticated access to set_cmd_process endpoint
    Send an HTTP POST request to http://[device-ip]/goform/goform_set_cmd_process without any authentication headers, including a basic parameter like 'cmd=reboot' or 'cmd=get_wan_info'
    Affected if Request is processed and returns success without requiring authentication

You are affected if you have a KuWFi CPF908-CP5 device running firmware WEB5.0_LCD_20210125 or earlier, and the /goform/goform_get_cmd_process or /goform/goform_set_cmd_process endpoints respond to unauthenticated requests.

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

Apply vendor firmware patch when available; until then, isolate affected devices behind firewalls or restrict network access to the web management interface to prevent unauthenticated attacks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43983 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43983 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