dbcve.org
Emg5723 T50k FirmwareOperating system · Zyxel

CVE-2024-11253

HIGH · 7.2 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to after 5.50 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 "DNSServer” parameter of the diagnostic function in the Zyxel VMG8825-T50K firmware version V5.50(ABOM.8.5)C0 and earlier 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 DNSServer parameter of the diagnostic function in Zyxel VMG8825-T50K firmware V5.50(ABOM.8.5)C0 and earlier. An authenticated attacker with administrator privileges can inject and execute arbitrary OS commands on the device through insufficient input validation of the DNSServer parameter.

MitigationUpdate the Zyxel VMG8825-T50K firmware to a version beyond V5.50(ABOM.8.5)C0. If no update is available, restrict administrator access to trusted users only and monitor for suspicious diagnostic tool usage.

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
Emg5723 T50k FirmwareOperating system
Affected:<= 5.50\(abom.8.5\)c0
Dm4200 B0 FirmwareOperating system
Affected:<= 5.17\(acbs.1\)c0
Vmg3927 T50k FirmwareOperating system
Affected:<= 5.50\(abom.8.5\)c0
Vmg4005 B50a FirmwareOperating system
Affected:<= 5.15\(abqa.2.3\)c0
Vmg4005 B60a FirmwareOperating system
Affected:<= 5.15\(abqa.2.3\)c0
Vmg8825 T50k FirmwareOperating system
Affected:<= 5.50\(abom.8.5\)c0

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 device model
    Locate the device model number on the device label or in the web interface (typically under Status, System Info, or General Setup pages)
    Affected if Device model is not one of the listed affected models (Emg5723 T50k, Dm4200 B0, Vmg3927 T50k, Vmg4005 B50a, Vmg4005 B60a, Vmg8825 T50k)
  2. Check firmware version
    Find the firmware version in the device web interface (usually under Administration, Firmware Upgrade, or Status pages) or via CLI command like 'cat /etc/zyfwinfo' or 'version'
    Affected if Firmware version is at or below 5.50(abom.8.5)c0 for T50k models, 5.17(acbs.1)c0 for Dm4200 B0, or 5.15(abqa.2.3)c0 for Vmg4005 models
  3. Verify diagnostic function accessibility
    Locate the diagnostic function in the web interface (typically under Maintenance, Diagnostics, Tools, or Network Diagnostics) and confirm it is accessible to administrator-level users
    Affected if Diagnostic function is exposed and accessible without additional access controls
  4. Inspect DNSServer parameter
    Access the diagnostic function and examine the DNSServer parameter field (often found in DNS or network diagnostic settings) for unexpected characters or patterns that may indicate injection
    Affected if DNSServer parameter accepts and processes shell metacharacters or executes input as commands

The device is affected if it is one of the listed Zyxel models running a firmware version at or below the specified threshold AND the diagnostic function with DNSServer parameter is accessible to administrator users.

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 5.50
Interim mitigation

Update the Zyxel VMG8825-T50K firmware to a version beyond V5.50(ABOM.8.5)C0. If no update is available, restrict administrator access to trusted users only and monitor for suspicious diagnostic tool usage.

Recommended fix Moderate confidence

Latest firmware version available from Zyxel for your specific model (must be higher than the affected versions: 5.50(abom.8.5)c0 for T50k models, 5.17(acbs.1)c0 for Dm4200 B0, 5.15(abqa.2.3)c0 for Vmg4005 models)

  1. 1. Identify the exact model number of your Zyxel device from the affected list (Emg5723 T50k, Dm4200 B0, Vmg3927 T50k, Vmg4005 B50a, Vmg4005 B60a, or Vmg8825 T50k)
  2. 2. Check the current firmware version on the device through the web management interface or CLI
  3. 3. Visit the official Zyxel support website (www.zyxel.com) and navigate to the firmware download section for your specific model
  4. 4. Download the latest available firmware version for your device
  5. 5. Back up the current device configuration before upgrading
  6. 6. Upload and install the new firmware following Zyxel's standard firmware upgrade procedure
  7. 7. After upgrade, verify the device is functioning correctly and the new firmware version is applied
  8. 8. Restore the configuration if needed and confirm the vulnerability is remediated
Caveat Firmware upgrades may reset device configuration; always backup before upgrading

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

Fix this in Emg5723 T50k Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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