dbcve.org
Aterm Wg1800hp4 FirmwareOperating system · Nec

CVE-2024-28011

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
Hidden Functionality 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 OS 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

Multiple NEC Aterm router models contain a hidden functionality (likely a backdoor) that allows unauthenticated remote attackers to execute arbitrary OS commands with root privileges via the internet. This is a critical remote code execution vulnerability affecting the firmware of the listed wireless router models.

MitigationApply vendor-provided firmware updates to all affected Aterm router models as soon as they become available. If patches are unavailable, disable remote administration interfaces, implement network segmentation, and restrict internet-facing access to these devices.

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 Wg1900hp2 FirmwareOperating system
Affected:all versions
Aterm Wg1200hp3 FirmwareOperating system
Affected:all versions
Aterm Wg1800hp3 FirmwareOperating system
Affected:all versions
Aterm Wg1200hs2 FirmwareOperating system
Affected:all versions
Aterm Wg1900hp FirmwareOperating system
Affected:all versions
Aterm Wg1200hp2 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
    Check the product label on the device or log into the router admin web interface (typically at 192.168.0.1 or 192.168.1.1) and look for the model name in the status or system information page
    Affected if The model is one of: Wg1800hp4, Wg1200hs3, Wg1900hp2, Wg1200hp3, Wg1800hp3, Wg1200hs2, Wg1900hp, or Wg1200hp2
  2. Confirm firmware version
    In the router admin web interface, navigate to the firmware or system information section to view the installed firmware version
    Affected if Any firmware version is installed on an affected model (all versions are vulnerable)
  3. Check if remote administration is enabled
    In the router admin web interface, look for settings named Remote Management, Remote Access, WAN Access, or Web Remote Configuration and verify whether they are enabled
    Affected if Remote administration or remote web access is enabled and the management interface is reachable from the internet/WAN side
  4. Scan for unexpected open ports on WAN interface
    Perform a port scan from outside your local network (or use an online port scanner) targeting the router public IP address, looking for open HTTP (port 80), HTTPS (port 443), or other unusual ports
    Affected if The router has open management ports (80, 443, or others) accessible from the internet

You are affected if you own any of the listed Aterm router models and remote administration or web management interfaces are accessible from the internet.

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

Apply vendor-provided firmware updates to all affected Aterm router models as soon as they become available. If patches are unavailable, disable remote administration interfaces, implement network segmentation, and restrict internet-facing access to these devices.

Fix this in Aterm Wg1800hp4 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA4.0 h
48.0 hours of engineering $8,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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