dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-0355

HIGH · 7.5 CVSS v3.1 Published 2025-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Missing Authentication for Critical Function vulnerability in NEC Corporation Aterm WG2600HS Ver.1.7.2 and earlier, WF1200CRS Ver.1.6.0 and earlier, WG1200CRS Ver.1.5.0 and earlier, GB1200PE Ver.1.3.0 and earlier, WG2600HP4 Ver.1.4.2 and earlier, WG2600HM4 Ver.1.4.2 and earlier, WG2600HS2 Ver.1.3.2 and earlier, WX3000HP Ver.2.4.2 and earlier and WX4200D5 Ver.1.2.4 and earlier allows a attacker to get a Wi-Fi password via the network.

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

Missing authentication vulnerability in NEC Aterm router series allows unauthenticated attackers on the network to retrieve Wi-Fi passwords. The critical function (Wi-Fi password retrieval) lacks authentication controls, enabling any network-adjacent attacker to obtain sensitive credentials without authorization.

MitigationUpdate affected router firmware to versions that include authentication requirements for critical functions. If updates are unavailable, implement network segmentation to restrict access to the router's management interface.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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 NEC Aterm router model
    Log into the router administration page or check the device label to confirm the model number is an NEC Aterm series router
    Affected if The device is not an NEC Aterm router - not affected
  2. Determine firmware version
    Access the router admin panel (typically at 192.168.0.1 or 192.168.1.1), navigate to System or Status settings, and record the firmware version displayed
    Affected if Unable to determine firmware version - manual verification required
  3. Verify Wi-Fi password retrieval requires authentication
    From a browser on a device connected to the network (not logged into admin), attempt to access common Wi-Fi password retrieval endpoints such as http://[router-ip]//cgi-bin/wlancfg or check if the wireless settings page prompts for login credentials
    Affected if Wi-Fi passwords or WPS PIN codes are displayed without requiring admin login - AFFECTED
  4. Test management interface exposure
    Access the router login page from an unauthenticated client on the LAN and confirm whether a valid session or login is required to view or export wireless configuration
    Affected if Wireless SSID and password fields are visible or exportable without authentication - AFFECTED

The environment is affected if the NEC Aterm router exposes Wi-Fi credentials (SSID/password) through its web interface without requiring administrator authentication, allowing any network-adjacent user to retrieve sensitive wireless keys.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected router firmware to versions that include authentication requirements for critical functions. If updates are unavailable, implement network segmentation to restrict access to the router's management interface.

Recommended fix Moderate confidence

Each model has a specific fixed version: WG2600HS to Ver.1.7.3 or later, WF1200CRS to Ver.1.6.1 or later, WG1200CRS to Ver.1.5.1 or later, GB1200PE to Ver.1.3.1 or later, WG2600HP4 to Ver.1.4.3 or later, WG2600HM4 to Ver.1.4.3 or later, WG2600HS2 to Ver.1.3.3 or later, WX3000HP to Ver.2.4.3 or later

  1. 1. Identify your Aterm router model from the affected list: WG2600HS, WF1200CRS, WG1200CRS, GB1200PE, WG2600HP4, WG2600HM4, WG2600HS2, WX3000HP, or WX4200D5
  2. 2. Access the router's administration interface via web browser (typically at 192.168.0.1 or 192.168.1.1)
  3. 3. Navigate to the firmware update or system settings section
  4. 4. Check the current firmware version under system information or status
  5. 5. Download the latest firmware version from NEC's official support page at jpn.nec.com for your specific model
  6. 6. In the firmware update section, upload the downloaded firmware file and initiate the update
  7. 7. Wait for the update to complete (do not power off the router)
  8. 8. After reboot, verify the firmware version has been updated to a version newer than the vulnerable version for your model
Caveat Minor: Firmware update may reset some router settings to defaults; reconfigure any custom settings after update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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