dbcve.org
Aterm Wg1800hp4 FirmwareOperating system · Nec

CVE-2024-28007

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper authentication vulnerability in NEC Corporation Aterm WG1800HP4, WG1200HS3, WG1900HP2, WG1200HP3, WG1800HP3, WG1200HS2, WG1900HP, WG1200HP2, W1200EX(-MS), WG1200HS, WG1200HP, WF300HP2, W300P, WF800HP, WR8165N, WG2200HP, WF1200HP2, WG1800HP2, WF1200HP, WG600HP, WG300HP, WF300HP, WG1800HP, WG1400HP, WR8175N, WR9300N, WR8750N, WR8160N, WR9500N, WR8600N, WR8370N, WR8170N, WR8700N, WR8300N, WR8150N, WR4100N, WR4500N, WR8100N, WR8500N, CR2500P, WR8400N, WR8200N, WR1200H, WR7870S, WR6670S, WR7850S, WR6650S, WR6600H, WR7800H, WM3400RN, WM3450RN, WM3500R, WM3600R, WM3800R, WR8166N, MR01LN MR02LN, WG1810HP(JE) and WG1810HP(MF) all versions allows a attacker to execute an arbitrary command with the root privilege via the internet.

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

Improper authentication vulnerability in NEC Aterm routers allows remote unauthenticated attackers to bypass authentication mechanisms and execute arbitrary commands with root privileges via the internet across all versions of numerous WG and WR series models.

MitigationImplement network segmentation to isolate affected devices from direct internet exposure; deploy firewall rules to restrict access to management interfaces; monitor for unauthorized access attempts; consider replacing end-of-life devices if vendor patches are unavailable.

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
Aterm Wg1800hp4 FirmwareOperating system
Affected:all versions
Aterm Wg1200hs3 FirmwareOperating system
Affected:all versions
Aterm Wr8750n FirmwareOperating system
Affected:all versions
Aterm Wr8160n FirmwareOperating system
Affected:all versions
Aterm Wr9500n FirmwareOperating system
Affected:all versions
Aterm Wr8600n FirmwareOperating system
Affected:all versions
Aterm Wr8370n FirmwareOperating system
Affected:all versions
Aterm Wr8170n FirmwareOperating system
Affected:all versions

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 router model
    Access the router web interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to the status or device information page to confirm the exact model name (e.g., WG1800HP4, WR8750N, etc.)
    Affected if The model matches any of these: WG1800HP4, WG1200HS3, WR8750N, WR8160N, WR9500N, WR8600N, WR8370N, WR8170N
  2. Verify firmware version
    In the router web interface, go to the firmware or software update section to view the installed firmware version
    Affected if Any firmware version is installed (the advisory states all versions are affected)
  3. Check WAN-side management settings
    In the router web interface, navigate to the advanced or administration settings and look for options labeled 'Remote Management', 'WAN Side Management', 'Internet-side Settings', or 'External Access'
    Affected if Remote management or WAN access to the admin interface is enabled
  4. Confirm internet exposure
    Check your firewall or NAT configuration to determine if the router's management interface (ports 80, 443, or custom admin ports) is reachable from the WAN/internet side
    Affected if The router admin interface is directly accessible from the internet (no firewall blocking WAN-to-admin ports)
  5. Review NAT/port forwarding rules
    Examine the router's NAT or port forwarding tables for any rules that forward traffic from the WAN interface to the router's internal IP on management ports
    Affected if Any port forwarding or NAT rule maps external traffic to the router's web interface ports

If you own any of the affected Aterm models and the device management interface is accessible from the internet (WAN side), you are affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network segmentation to isolate affected devices from direct internet exposure; deploy firewall rules to restrict access to management interfaces; monitor for unauthorized access attempts; consider replacing end-of-life devices if vendor patches are unavailable.

Fix this in Aterm Wg1800hp4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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-2024-28007 — 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-2024-28007 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