dbcve.org
Emg6726 B10a FirmwareOperating system · Zyxel

CVE-2024-9200

HIGH · 7.2 CVSS v3.1 Published 2024-12-03
Fix available
A fix is available. Upgrade to 5.13 / 5.15 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A post-authentication command injection vulnerability in the "host" parameter of the diagnostic function in Zyxel VMG4005-B50A firmware versions through V5.15(ABQA.2.2)C0 could allow an authenticated attacker with administrator privileges to execute operating system (OS) commands on a vulnerable device.

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

A post-authentication command injection vulnerability exists in the diagnostic function of Zyxel VMG4005-B50A routers. The 'host' parameter in the diagnostic feature does not properly sanitize user input, allowing an authenticated administrator to inject and execute arbitrary OS commands on the device.

MitigationApply the latest vendor firmware patch when available; until then, restrict administrative access to trusted IPs only and consider network segmentation to limit exposure, as the vulnerability requires admin-level authentication.

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
Emg6726 B10a FirmwareOperating system
Affected:< 5.13\(abnp.8\)c1
Vmg3927 B50b FirmwareOperating system
Affected:< 5.13\(ably.9\)c1
Vmg4005 B50a FirmwareOperating system
Affected:< 5.15\(abqa.2.3\)c0
Vmg4005 B60a FirmwareOperating system
Affected:< 5.15\(abqa.2.3\)c0
Vmg4005 B50b FirmwareOperating system
Affected:< 5.13\(abrl.5.2\)c0
Vmg4927 B50a FirmwareOperating system
Affected:< 5.13\(ably.9\)c1

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 checks

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

  1. Identify the router model
    Check the device label or web interface for the exact model number (e.g., VMG4005-B50A, VMG3927-B50B, etc.)
    Affected if The model is one of: EMG6726-B10A, VMG3927-B50B, VMG4005-B50A, VMG4005-B60A, VMG4005-B50B, or VMG4927-B50A
  2. Check the installed firmware version
    Access the router web interface (typically at 192.168.1.1) and navigate to Status or Maintenance > Firmware to view the current firmware version
    Affected if The firmware version is lower than the fixed version for your specific model (Emg6726 < 5.13(abnp.8)c1, Vmg3927 < 5.13(ably.9)c1, Vmg4005-B50A/B60A < 5.15(abqa.2.3)c0, Vmg4005-B50B < 5.13(abrl.5.2)c0, Vmg4927 < 5.13(ably.9)c1)
  3. Verify admin credentials exist
    Check if there are active administrator accounts configured on the device under User Account or Administrator settings
    Affected if At least one administrator account is configured and enabled on the router
  4. Check diagnostic feature accessibility
    Locate the diagnostic or ping test function in the router web interface, typically under Advanced Settings, Network Diagnostics, or Troubleshooting
    Affected if The diagnostic feature with a 'host' or 'ping' parameter is accessible to authenticated administrators

You are affected if your Zyxel router model matches one of the six listed models AND your firmware version is below the specified patch level for that model, and an administrator account exists on the device.

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 5.13 / 5.15 or later
Fixed in 5.135.15
Interim mitigation

Apply the latest vendor firmware patch when available; until then, restrict administrative access to trusted IPs only and consider network segmentation to limit exposure, as the vulnerability requires admin-level authentication.

Recommended fix High confidence

Zyxel firmware 5.13(abnp.8)c1 / 5.13(ably.9)c1 / 5.15(abqa.2.3)c0 / 5.13(abrl.5.2)c0 depending on device model

  1. 1. Identify the exact model number and current firmware version of the Zyxel device from the web GUI or label on the device
  2. 2. Navigate to Zyxel support website (www.zyxel.com) and locate the firmware download section for your specific device model
  3. 3. Download the firmware version equal to or newer than the fixed version for your model: Emg6726 B10a → 5.13(abnp.8)c1, Vmg3927 B50b → 5.13(ably.9)c1, Vmg4005 B50a → 5.15(abqa.2.3)c0, Vmg4005 B60a → 5.15(abqa.2.3)c0, Vmg4005 B50b → 5.13(abrl.5.2)c0, Vmg4927 B50a → 5.13(ably.9)c1
  4. 4. Log in to the device web interface with administrator credentials
  5. 5. Navigate to Administration > Firmware Upgrade or similar section
  6. 6. Upload the downloaded firmware file and initiate the upgrade process
  7. 7. Wait for the upgrade to complete and the device to reboot automatically
  8. 8. Verify the new firmware version is installed and the device is functioning normally
Caveat Standard firmware upgrade risk; ensure stable power during upload; backup configuration if possible

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

Fix this in Emg6726 B10a 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 the upgrade done

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-9200 — 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-9200 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