dbcve.org
ZldOperating system · Zyxel

CVE-2023-37925

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-28
Fix available
A fix is available. Upgrade to 6.70 / 6.80 or later.
See remediation →
57/100
Remediation priority · Elevated
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
An improper privilege management vulnerability in the debug CLI command of the Zyxel ATP series firmware versions 4.32 through 5.37, USG FLEX series firmware versions 4.50 through 5.37, USG FLEX 50(W) series firmware versions 4.16 through 5.37, USG20(W)-VPN series firmware versions 4.16 through 5.37, VPN series firmware versions 4.30 through 5.37, NWA50AX firmware version 6.29(ABYW.2), WAC500 firmware version 6.65(ABVS.1), WAX300H firmware version 6.60(ACHF.1), and WBE660S firmware version 6.65(ACGG.1), could allow an authenticated local attacker to access system files on an affected device.

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

This is an improper privilege management vulnerability in the debug CLI command of multiple Zyxel network security appliance series (ATP, USG FLEX, VPN, NWA, WAC, WAX, WBE). An authenticated local attacker can exploit the debug CLI to access system files on affected devices, representing a privilege escalation and information disclosure issue.

MitigationApply vendor-supplied firmware patches for the affected versions (firmware 5.38 or later for most series). If immediate patching is not possible, restrict physical and administrative access to the device CLI and monitor for unauthorized debug command usage.

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
ZldOperating system
Affected:>= 4.32, <= 5.37>= 4.50, <= 5.37>= 4.16, <= 5.37>= 4.30, <= 5.37
Nwa110ax FirmwareOperating system
Affected:< 6.70\(abtg.0\)
Nwa1123acv3 FirmwareOperating system
Affected:< 6.70\(abvt.0\)
Nwa210ax FirmwareOperating system
Affected:< 6.70\(abtd.0\)
Nwa220ax 6e FirmwareOperating system
Affected:< 6.70\(acco.0\)
Nwa50ax FirmwareOperating system
Affected:< 6.80\(abyw.0\)
Nwa50ax Pro FirmwareOperating system
Affected:< 6.80\(acge.0\)
Nwa55axe FirmwareOperating system
Affected:< 6.80\(abzl.0\)

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 and firmware version
    Access the device CLI or web interface and run 'show version' or check System > Firmware to determine the exact model (ATP, USG FLEX, VPN, NWA, WAC, WAX, WBE series) and current firmware version
    Affected if The device is one of the listed series and the firmware version falls within the affected ranges (< 5.38 for Zld versions, < 6.70 or < 6.80 for NWA models)
  2. Verify debug CLI command availability
    Log into the device CLI with administrative credentials and attempt to access the debug command mode (typically 'debug' or 'system debug' command), or check if the debug CLI is listed in the available command set
    Affected if The debug CLI command is accessible to authenticated users without additional privilege verification
  3. Check for debug command execution logs
    Review system logs (via CLI 'show log' or web interface logs) for any entries containing 'debug' command execution, particularly file access operations
    Affected if Debug commands have been executed, indicating potential exploitation or testing in the environment
  4. Inspect user privilege assignments
    Examine the device user database and privilege levels (typically via 'show user' or in the web interface under User/Administrator settings) to confirm which accounts have access to debug functionality
    Affected if Standard user accounts (non-root/admin) have access to debug CLI functionality

The environment is affected if the device model matches the listed series AND the installed firmware version is within the vulnerable ranges, AND the debug CLI feature is accessible to authenticated users.

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.

dbcve · scoped
Upgrade available Upgrade to 6.70 / 6.80 or later
Fixed in 6.706.80
Interim mitigation

Apply vendor-supplied firmware patches for the affected versions (firmware 5.38 or later for most series). If immediate patching is not possible, restrict physical and administrative access to the device CLI and monitor for unauthorized debug command usage.

Recommended fix High confidence

Nwa110ax/Nwa1123acv3/Nwa210ax/Nwa220ax 6e: >= 6.70; Nwa50ax/Nwa50ax Pro/Nwa55axe: >= 6.80

  1. Identify the specific NWA model from the affected device list (Nwa110ax, Nwa1123acv3, Nwa210ax, Nwa220ax 6e, Nwa50ax, Nwa50ax Pro, or Nwa55axe)
  2. Download the corresponding firmware version from Zyxel's official support website (www.zyxel.com)
  3. For Nwa110ax, Nwa1123acv3, Nwa210ax, Nwa220ax 6e: upgrade to firmware version 6.70 or later (e.g., 6.70(abtg.0), 6.70(abvt.0), 6.70(abtd.0), 6.70(acco.0) respectively)
  4. For Nwa50ax: upgrade to firmware version 6.80 or later (e.g., 6.80(abyw.0))
  5. For Nwa50ax Pro: upgrade to firmware version 6.80 or later (e.g., 6.80(acge.0))
  6. For Nwa55axe: upgrade to firmware version 6.80 or later (e.g., 6.80(abzl.0))
  7. Upload and apply the firmware through the device's web management interface or CLI
  8. Verify the upgrade was successful and the firmware version matches the target
Caveat Review Zyxel release notes for any configuration or feature changes between versions; backup configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zld Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37925 — 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-37925 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