CVE-2025-0356
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 · uneditedNEC Corporation Aterm WX1500HP Ver.1.4.2 and earlier and WX3600HP Ver.1.5.3 and earlier allows a attacker to execute arbitrary OS commands 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 confidenceNEC Aterm WX1500HP and WX3600HP routers contain a command injection vulnerability in firmware versions 1.4.2/1.5.3 and earlier that allows authenticated or unauthenticated remote attackers to execute arbitrary operating system commands via the network interface, likely through insufficient input validation in the web 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLog into the router web management interface and check the device status or system information page to confirm the model is WX1500HP or WX3600HPAffected if The model is WX1500HP or WX3600HP and the firmware version is at or below the affected versions
-
Check the installed firmware versionAccess the router web interface, navigate to the system status or firmware information page, and note the firmware version number displayedAffected if Firmware version is 1.4.2 or earlier for WX1500HP, or 1.5.3 or earlier for WX3600HP
-
Verify web management interface accessibilityCheck if the router web management interface (HTTP/HTTPS on ports 80/443 or vendor-default ports) is accessible from the internet or an untrusted network segment by attempting to access the router IP from an external location or reviewing firewall rulesAffected if The web management interface is exposed to untrusted networks without access restrictions
The environment is affected if the router is a WX1500HP or WX3600HP model running firmware version 1.4.2 or earlier (WX1500HP) or 1.5.3 or earlier (WX3600HP), and the web management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor-supplied firmware updates (WX1500HP Ver.1.4.3 or later, WX3600HP Ver.1.5.4 or later) to patch the command injection vulnerability, and restrict network access to the router's management interface.
Contact NEC for specific fixed firmware version (newer than WX1500HP Ver.1.4.2 and WX3600HP Ver.1.5.3)
- 1. Identify the exact model of your NEC Aterm router (WX1500HP or WX3600HP)
- 2. Contact NEC Corporation technical support to obtain the specific firmware version that addresses CVE-2025-0356
- 3. Download the official patched firmware from NEC's support website or obtain it directly from NEC technical support
- 4. Follow NEC's official firmware update instructions to apply the patch
- 5. After updating, verify the firmware version has been successfully changed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0356 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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