Categories
CVE-2025-12940 medium CVSS 5.5

Vulnerability in Netgear WAX610 (CVE-2025-12940)

Summary

Vulnerability in Netgear WAX610 (CVE-2025-12940). Confidential information can be exposed externally.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-12940 has been found in Netgear WAX610.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Netgear WAX610 CVE-2025-12940" on the vendor's site.

CVE-2025-12940 (Netgear WAX610) — CWE-532 / CVSS v3 5.5
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-532) exists in Netgear WAX610.

📍 Affected scope

Check the vendor advisory for the affected versions of Netgear WAX610.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'WAX610' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'WAX610' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で WAX610 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details