dbcve.org
Nr5307 FirmwareOperating system · Zyxel

CVE-2026-0711

MEDIUM · 6.8 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 1.60 / 2.00 or later.
See remediation →
70/100
Remediation priority · Elevated
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 EasyMesh-related APIs of Zyxel DX3300-T0 firmware versions through 5.50(ABVY.7.1)C0 could allow an authenticated, adjacent attacker with administrator privileges to execute OS commands on an affected 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

This is a post-authentication command injection vulnerability in Zyxel DX3300-T0 routers. An authenticated attacker with administrator privileges can inject arbitrary OS commands through EasyMesh-related API endpoints. The vulnerability exists in firmware versions up to 5.50(ABVY.7.1)C0 and allows complete compromise of the device after successful authentication.

MitigationApply the vendor firmware patch when available. Until then, restrict administrative access to trusted users only and implement network segmentation to limit exposure to adjacent network attackers.

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
Nr5307 FirmwareOperating system
Affected:< 2.00\(acjt.3\)c0
Nebula Fwa515 FirmwareOperating system
Affected:< 1.60\(acpz.0\)v0
Dx3300 T0 FirmwareOperating system
Affected:< 5.50\(abvy.7.2\)c0
Dx3300 T1 FirmwareOperating system
Affected:< 5.50\(abvy.7.2\)c0
Dx3301 T0 FirmwareOperating system
Affected:< 5.50\(abvy.7.2\)c0
Dx5401 B0 FirmwareOperating system
Affected:< 5.17\(abyo.7.2\)c0
Dx5401 B1 FirmwareOperating system
Affected:< 5.17\(abyo.7.2\)c0
Ee3301 00 FirmwareOperating system
Affected:< 5.63\(acmu.3.1\)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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 your Zyxel device model
    Locate the model number on the device label or check the web management interface for the exact model designation (e.g., DX3300-T0, Nr5307, Dx5401-B0)
    Affected if The device model matches one of the affected models listed in the CVE
  2. Check the installed firmware version
    Access the router web interface and navigate to the Status or System Info page to view the firmware version, or use the command line and run 'show version' or check /proc/version if SSH/telnet is available
    Affected if The firmware version is lower than the version threshold for your specific model (Nr5307 < 2.00(acjt.3)c0, Nebula Fwa515 < 1.60(acpz.0)v0, Dx3300-T0/T1 and Dx3301-T0 < 5.50(abvy.7.2)c0, Dx5401-B0/B1 < 5.17(abyo.7.2)c0, Ee3301-00 < 5.63(acmu.3.1)c0)
  3. Verify EasyMesh API functionality is enabled
    Check the router web interface for EasyMesh or Mesh networking settings, typically found under Wireless or Network settings, and confirm if the EasyMesh API service is active
    Affected if EasyMesh API functionality is enabled on the device
  4. Confirm administrative access is available
    Determine if you have administrator-level credentials for the device, or check if the management interface is accessible from the WAN or adjacent network segments
    Affected if The device management interface with admin privileges is accessible from the network segment where the attacker would be positioned

You are affected if your Zyxel device model and firmware version match one of the vulnerable combinations listed, and the EasyMesh API is enabled with administrative access possible from your network.

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 1.60 / 2.00 / 5.17 or later
Fixed in 1.602.005.17
Interim mitigation

Apply the vendor firmware patch when available. Until then, restrict administrative access to trusted users only and implement network segmentation to limit exposure to adjacent network attackers.

Recommended fix High confidence

Upgrade to vendor-provided firmware >= 2.00(acjt.3)c0 for Nr5307, >= 1.60(acpz.0)v0 for Nebula Fwa515, >= 5.50(abvy.7.2)c0 for Dx3300-T0/T1 and Dx3301-T0, >= 5.17(abyo.7.2)c0 for Dx5401-B0/B1, >= 5.63(acmu.3.1)c0 for EE3301-00

  1. Identify the exact model number of your Zyxel device from the affected list (Nr5307, Nebula Fwa515, Dx3300-T0, Dx3300-T1, Dx3301-T0, Dx5401-B0, Dx5401-B1, or EE3301-00)
  2. Navigate to the Zyxel support website (www.zyxel.com) and locate the firmware download section for your specific device model
  3. Download the latest firmware version that matches or exceeds the fixed release for your model: Nr5307: 2.00(acjt.3)c0, Nebula Fwa515: 1.60(acpz.0)v0, Dx3300-T0/T1 and Dx3301-T0: 5.50(abvy.7.2)c0, Dx5401-B0/B1: 5.17(abyo.7.2)c0, EE3301-00: 5.63(acmu.3.1)c0
  4. Log into the device web management interface with administrator credentials
  5. Locate the Firmware Upgrade or System Maintenance section in the administrative UI
  6. Upload the downloaded firmware file and initiate the upgrade process
  7. Wait for the device to complete the firmware update and reboot automatically
  8. Verify the firmware version has been updated by checking the device status page after reboot
Caveat Standard firmware upgrade risk applies - ensure stable power during upload; backup configuration if possible; device may briefly go offline during upgrade process

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

Fix this in Nr5307 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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