dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Wnap320 FirmwareOperating system · Netgear

CVE-2016-1555

CRITICAL · 9.8 CVSS v3.1 Published 2017-04-21
Fix available
A fix is available. Upgrade to after 3.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear WN604 before 3.3.3 and WN802Tv2, WNAP210v2, WNAP320, WNDAP350, WNDAP360, and WNDAP660 before 3.5.5.0 allow remote attackers to execute arbitrary commands.

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

Multiple Netgear wireless access point devices (WN604, WN802Tv2, WNAP210v2, WNAP320, WNDAP350, WNDAP360, WNDAP660) contain command injection vulnerabilities in boardData PHP files. Remote attackers can execute arbitrary commands via unspecified vectors in these files, likely through unsanitized input being passed to system calls.

MitigationUpdate Netgear device firmware to version 3.3.3 or later for WN604, and version 3.5.5.0 or later for other affected models. If patching is not immediately feasible, restrict administrative interface access to trusted networks or disable the affected PHP endpoints.

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
Wnap320 FirmwareOperating system
Affected:<= 3.0.5.0
Wndap350 FirmwareOperating system
Affected:<= 3.0.5.0
Wndap360 FirmwareOperating system
Affected:<= 3.0.5.0
Wndap210v2 FirmwareOperating system
Affected:<= 3.0.5.0
Wn604 FirmwareOperating system
Affected:<= 3.3.2
Wndap660 FirmwareOperating system
Affected:<= 3.0.5.0
Wn802tv2 FirmwareOperating system
Affected:<= 3.0.5.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Netgear device model
    Access the device's web administration interface and look at the model information, typically found on the status or administration page, or check the physical device label
    Affected if The device model is one of: WN604, WNAP320, WNDAP350, WNDAP360, WNDAP210v2, WNDAP660, or WN802tv2
  2. Determine the installed firmware version
    In the device web interface, navigate to the Administration or Maintenance section and locate the firmware version field. This information may also be available via SNMP or by accessing the device via SSH/Telnet and running the appropriate show command
    Affected if The firmware version cannot be determined or is not visible
  3. Compare firmware version against affected ranges
    If firmware version is 3.0.5.0 or lower for WNAP320, WNDAP350, WNDAP360, WNDAP210v2, WNDAP660, or WN802tv2, or 3.3.2 or lower for WN604, the device is in the affected version range
    Affected if The installed firmware version falls within: WNAP320/WNDAP350/WNDAP360/WNDAP210v2/WNDAP660/WN802tv2 <= 3.0.5.0, or WN604 <= 3.3.2
  4. Verify remote management access is enabled
    Check the device configuration for remote management settings, typically under Administration > Remote Management or similar. Confirm whether the web interface (PHP services) is accessible from untrusted networks
    Affected if Remote administration or web interface access is enabled and reachable from untrusted networks

A defender is affected if they have any of the listed Netgear device models running firmware versions at or below the affected thresholds, with the web interface accessible.

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 a release after 3.3.2
Vendor patch kb.netgear.com →
Interim mitigation

Update Netgear device firmware to version 3.3.3 or later for WN604, and version 3.5.5.0 or later for other affected models. If patching is not immediately feasible, restrict administrative interface access to trusted networks or disable the affected PHP endpoints.

Recommended fix High confidence

WN604: upgrade to firmware 3.3.3 or later; WNAP320/WNDAP350/WNDAP360/WNDAP210v2/WNDAP660/WN802Tv2: upgrade to firmware 3.5.5.0 or later

  1. Identify the exact Netgear device model (WN604, WNAP320, WNDAP350, WNDAP360, WNDAP210v2, WNDAP660, or WN802Tv2)
  2. Access the device's web administration interface
  3. Navigate to the firmware upgrade or administration section
  4. Check the current firmware version under the status or maintenance page
  5. Download the appropriate fixed firmware from the official Netgear support site (kb.netgear.com)
  6. Upload and install the new firmware version via the web interface, or via TFTP if the web interface is unavailable
  7. After upgrade, verify the firmware version has been updated to the fixed release
  8. Confirm the boardData102.php, boardData103.php, boardDataJP.php, boardDataNA.php, and boardDataWW.php files have been updated or removed
Caveat Firmware upgrades may reset device configuration to defaults; backup configuration before upgrading and restore after

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

Fix this in Wnap320 Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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