dbcve.org
K2 FirmwareOperating system · Phicomm

CVE-2023-40796

HIGH · 7.8 CVSS v3.1 Published 2023-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Phicomm k2 v22.6.529.216 was discovered to contain a command injection vulnerability via the function luci.sys.call.

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 confidence

Command injection vulnerability in Phicomm K2 router firmware v22.6.529.216 allows attackers to execute arbitrary OS commands through the luci.sys.call function in the LuCI web interface.

MitigationUpdate to a patched firmware version if available; otherwise, restrict access to the LuCI admin interface or disable the vulnerable luci.sys.call functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
K2 FirmwareOperating system
Affected:= 22.6.529.216

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify firmware version
    Access the router admin panel or check system settings to view the installed firmware version. Alternatively, check the router's web interface or use commands like 'cat /proc/version' or 'uname -a' via SSH if available.
    Affected if The installed firmware version is exactly 22.6.529.216
  2. Confirm LuCI web interface is enabled
    Access the router's web interface at the typical LuCI path (usually /cgi-bin/luci or /luci) using a browser. Log in to the admin panel and navigate to the system or status page to confirm LuCI is active.
    Affected if The LuCI web interface is accessible and functional on the device
  3. Verify luci.sys.call function exists
    If you have SSH or telnet access to the router, check for the presence of the Lua luci.sys.call function by examining the LuCI configuration files in /usr/lib/lua/luci/ or by attempting to invoke it through the web interface.
    Affected if The luci.sys.call function is present and exposed through the LuCI interface

A user is affected if their Phicomm K2 router is running firmware version 22.6.529.216 AND the LuCI web interface with the vulnerable luci.sys.call function is accessible.

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

Update to a patched firmware version if available; otherwise, restrict access to the LuCI admin interface or disable the vulnerable luci.sys.call functionality.

Fix this in K2 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-40796 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