dbcve.org
Wax610y FirmwareOperating system · Netgear

CVE-2025-12940

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 11.8.0.10 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
Login credentials are inadvertently recorded in logs if a Syslog Server is configured in NETGEAR WAX610 and WAX610Y (AX1800 Dual Band PoE Multi-Gig Insight Managed WiFi 6 Access Points). An user having access to the syslog server can read the logs containing these credentials.  This issue affects WAX610: before 10.8.11.4; WAX610Y: before 10.8.11.4. Devices managed with Insight get automatic updates. If not, please check the firmware version and update to the latest. Fixed in: WAX610 firmware 11.8.0.10 or later. WAX610Y firmware 11.8.0.10 or later.

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

Login credentials are being recorded in plaintext syslog messages when a Syslog Server is configured on NETGEAR WAX610 and WAX610Y access points. Any user with access to the syslog server or its logs can read these exposed credentials.

MitigationUpdate firmware on affected devices to version 11.8.0.10 or later. For devices managed through Insight, verify automatic updates are enabled; for unmanaged devices, manually apply the firmware update.

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
Wax610y FirmwareOperating system
Affected:< 11.8.0.10
Wax610 FirmwareOperating system
Affected:< 11.8.0.10

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 your access point model
    Log into the NETGEAR web UI or CLI and check the device model under System Information or similar. Look for WAX610 or WAX610Y designations.
    Affected if The device is a NETGEAR WAX610 or WAX610Y access point.
  2. Check the installed firmware version
    In the web UI, navigate to System > Management > Firmware Update, or use the CLI command 'show version' to display the current firmware version. Note the exact version number.
    Affected if The firmware version is less than 11.8.0.10.
  3. Verify if Syslog Server is configured
    In the web UI, go to System > Management > Syslog Server or similar section. Check if a remote syslog server IP address or hostname is configured and enabled.
    Affected if A Syslog Server is configured and enabled on the device.
  4. Inspect syslog messages for plaintext credentials
    If syslog is configured, review the logs on your syslog server or the device logs. Search for login events, authentication attempts, or configuration saves that may contain username and password strings in plaintext.
    Affected if Plaintext login credentials appear in syslog messages.

You are affected if you have a WAX610 or WAX610Y device with firmware below 11.8.0.10 that has Syslog Server configured, with exposed credentials visible in the syslog output.

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

Update firmware on affected devices to version 11.8.0.10 or later. For devices managed through Insight, verify automatic updates are enabled; for unmanaged devices, manually apply the firmware update.

Recommended fix High confidence

WAX610/WAX610Y firmware 11.8.0.10 or later

  1. Check the current firmware version on the WAX610 or WAX610Y device through the web management interface or Insight portal
  2. Download the latest firmware version 11.8.0.10 or later from the official NETGEAR support website (kb.netgear.com or www.netgear.com)
  3. Access the device's web management interface and navigate to the firmware update section
  4. Upload the downloaded firmware file and initiate the update process
  5. Wait for the device to reboot and verify the firmware has been updated to 11.8.0.10 or later
  6. If the device is managed by Insight, ensure automatic updates are enabled to receive future patches

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

Fix this in Wax610y 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-2025-12940 — 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-2025-12940 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