CVE-2025-13942
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 · uneditedA command injection vulnerability in the UPnP function of the Zyxel EX3510-B0 firmware versions through 5.17(ABUP.15.1)C0 could allow a remote attacker to execute operating system (OS) commands on an affected device by sending specially crafted UPnP SOAP requests.
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 confidenceA command injection vulnerability exists in the UPnP function of Zyxel EX3510-B0 devices. Attackers can send specially crafted UPnP SOAP requests to inject and execute arbitrary operating system commands on the affected device. This is a pre-authentication remote vulnerability with CVSS 9.8 critical severity.
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< 5.18\(acgj.0.5\)c0< 1.00\(abqu.9\)c0< 1.18\(acca.6\)v0< 1.00\(abuv.12\)b2< 1.16\(accc.1\)v0< 5.17\(abyl.10.1\)c0< 5.17\(abyl.10.1\)c0< 5.19\(acjq.4.1\)c0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and confirm it is in the affected product listAccess the device admin interface or check the device label to determine the exact model (e.g., Wx5610 B0, Lte3301 Plus, Nr7101, Dx4510 B0/B1, Ee6510 10). Cross-reference against the list of affected models in the CVE.Affected if The device model matches one of the following: Wx5610 B0, Lte3301 Plus, Nebula Lte3301 Plus, Nr7101, Nebula Nr7101, Dx4510 B0, Dx4510 B1, or Ee6510 10.
-
Check installed firmware version against affected version rangesAccess the device admin interface (typically via web UI or CLI) and navigate to the firmware or system information section. Note the exact firmware version string (e.g., 5.18(acgj.0.5)c0). Compare against the version thresholds: Wx5610 B0 < 5.18(acgj.0.5)c0, Lte3301 Plus < 1.00(abqu.9)c0, Nebula Lte3301 Plus < 1.18(acca.6)v0, Nr7101 < 1.00(abuv.12)b2, Nebula Nr7101 < 1.16(accc.1)v0, Dx4510 B0/B1 < 5.17(abyl.10.1)c0, Ee6510 10 < 5.19(acjq.4.1)c0.Affected if The installed firmware version is lower than the threshold version for your specific model.
-
Confirm UPnP is enabled on the deviceAccess the device admin interface and navigate to the UPnP settings section (usually under Network, Advanced, or LAN settings). Verify whether the UPnP function is turned ON or enabled.Affected if UPnP is currently enabled on the device. Note that disabling UPnP reduces the attack surface but does not eliminate risk if the device is already compromised.
-
Verify network exposure of the UPnP serviceCheck the device network configuration to determine if UPnP is exposed to the WAN/internet interface. This can be done by reviewing port forwarding rules, firewall settings, or by scanning the external IP for UPnP SSDP responses (port 1900/UDP).Affected if UPnP is accessible from the WAN/internet side or the device is directly exposed to untrusted networks without firewall protection.
The device is affected if it is one of the listed Zyxel models running firmware below the specified threshold AND has UPnP enabled and/or exposed, making it vulnerable to pre-authentication command injection via crafted UPnP SOAP requests.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.001.161.18
Apply the latest firmware update from Zyxel when available. As an interim measure, disable UPnP on the device if not required, and place the device behind a restrictive firewall to limit external attack surface.
Upgrade to firmware version >= 5.18(acgj.0.5)c0 for Wx5610 B0, >= 1.00(abqu.9)c0 for Lte3301 Plus, >= 1.18(acca.6)v0 for Nebula Lte3301 Plus, >= 1.00(abuv.12)b2 for Nr7101, >= 1.16(accc.1)v0 for Nebula Nr7101, >= 5.17(abyl.10.1)c0 for Dx4510 B0/B1, or >= 5.19(acjq.4.1)c0 for Ee6510 10
- 1. Identify the exact model number of your Zyxel device from the affected list (Wx5610 B0, Lte3301 Plus, Nebula Lte3301 Plus, Nr7101, Nebula Nr7101, Dx4510 B0, Dx4510 B1, or Ee6510 10)
- 2. Access the device administration interface or Zyxel support portal to check the current firmware version
- 3. Navigate to the firmware download/support section for your specific model on www.zyxel.com
- 4. Download the latest stable firmware version that meets or exceeds the fixed version for your model
- 5. Back up the device configuration before performing the firmware upgrade
- 6. Upload and install the new firmware following the vendor's standard upgrade procedure
- 7. Verify the upgrade was successful and confirm the new firmware version matches the fixed version or newer
- 8. After upgrade, verify the UPnP service is functioning properly and consider disabling UPnP if not required
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13942 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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