dbcve.org
Nwa50ax FirmwareOperating system · Zyxel

CVE-2024-1575

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-23
Fix available
A fix is available. Upgrade to 7.00 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The improper privilege management vulnerability in the Zyxel WBE660S firmware version 6.70(ACGG.3) and earlier versions could allow an authenticated user to escalate privileges and download the configuration files on a vulnerable 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 · moderate confidence

The Zyxel WBE660S access point firmware versions 6.70(ACGG.3) and earlier contain improper privilege management that allows an authenticated user to escalate privileges beyond what their account should permit, enabling unauthorized download of device configuration files containing sensitive system data.

MitigationApply the vendor firmware update when available; restrict administrative access to trusted personnel only and monitor for unauthorized configuration exports.

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
Nwa50ax FirmwareOperating system
Affected:< 7.00\(abyw.1\)
Nwa50ax Pro FirmwareOperating system
Affected:< 7.00\(acge.1\)
Nwa55axe FirmwareOperating system
Affected:< 7.00\(abzl.1\)
Nwa90ax FirmwareOperating system
Affected:< 7.00\(accv.1\)
Nwa90ax Pro FirmwareOperating system
Affected:< 7.00\(acgf.1\)
Nwa110ax FirmwareOperating system
Affected:< 7.00\(abtg.1\)
Nwa210ax FirmwareOperating system
Affected:< 7.00\(abtd.1\)
Nwa220ax 6e FirmwareOperating system
Affected:< 7.00\(acco.1\)

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

CVSS:3.1/AV:N/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 the access point model
    Log into the Zyxel device web interface or check the physical device label to confirm the exact model number (e.g., NWA50AX, NWA110AX, etc.)
    Affected if The model is one of: Nwa50ax, Nwa50ax Pro, Nwa55axe, Nwa90ax, Nwa90ax Pro, Nwa110ax, Nwa210ax, or Nwa220ax 6e
  2. Check the installed firmware version
    Access the device web interface, navigate to Maintenance > Firmware > Firmware Upgrade, or use the CLI command 'show system-info' to retrieve the current firmware version
    Affected if The firmware version is earlier than 7.00(abyw.1) for Nwa50ax, 7.00(acge.1) for Nwa50ax Pro, 7.00(abzl.1) for Nwa55axe, 7.00(accv.1) for Nwa90ax, 7.00(acgf.1) for Nwa90ax Pro, 7.00(abtg.1) for Nwa110ax, 7.00(abtd.1) for Nwa210ax, or 7.00(acco.1) for Nwa220ax 6e
  3. Verify if local user accounts exist
    In the web interface, go to Configuration > Object > User or use the CLI 'show user' command to list configured accounts
    Affected if Any local user account is configured on the device, since the vulnerability allows privilege escalation for any authenticated user
  4. Check for unauthorized configuration exports
    Review device logs under Maintenance > Log or use 'show log' CLI command for entries containing 'download config', 'export config', or configuration file access events
    Affected if Unexpected configuration export activities are present in the logs, particularly from accounts that should not have administrative privileges

The environment is affected if the device model is one of the listed NWA series access points and the installed firmware version is below the corresponding 7.00 threshold for that model.

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 7.00 or later
Fixed in 7.00
Interim mitigation

Apply the vendor firmware update when available; restrict administrative access to trusted personnel only and monitor for unauthorized configuration exports.

Recommended fix Moderate confidence

Firmware 7.00 with the model-specific build code (abyw.1, acge.1, abzl.1, accv.1, acgf.1, abtg.1, abtd.1, or acco.1)

  1. 1. Identify the exact NWA model (e.g., NWA50AX, NWA50AX Pro, NWA55AXE, NWA90AX, NWA90AX Pro, NWA110AX, NWA210AX, NWA220AX 6e) from the device label or management interface
  2. 2. Navigate to Zyxel support website (www.zyxel.com) and locate the firmware download section
  3. 3. Search for the specific model and download firmware version 7.00 with the corresponding build code: NWA50AX: 7.00(abyw.1), NWA50AX Pro: 7.00(acge.1), NWA55AXE: 7.00(abzl.1), NWA90AX: 7.00(accv.1), NWA90AX Pro: 7.00(acgf.1), NWA110AX: 7.00(abtg.1), NWA210AX: 7.00(abtd.1), NWA220AX 6e: 7.00(acco.1)
  4. 4. Access the device web management interface or CLI
  5. 5. Navigate to Maintenance > Firmware Upgrade (or equivalent)
  6. 6. Upload the downloaded firmware file and initiate the upgrade
  7. 7. Wait for the upgrade to complete and the device to reboot
  8. 8. Verify the firmware version in the device management interface to confirm the fix
Caveat Review Zyxel release notes for any configuration or feature changes between current version and 7.00; test in non-production environment first

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

Fix this in Nwa50ax Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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