CVE-2025-43879
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 · uneditedWRH-733GBK and WRH-733GWH contain an improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability in the telnet function. If a remote unauthenticated attacker sends a specially crafted request to the affected product, an arbitrary OS command may be executed.
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 confidenceOS command injection vulnerability in the telnet function of WRH-733GBK and WRH-733GWH devices allows remote unauthenticated attackers to execute arbitrary OS commands via specially crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.0/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.
-
Confirm device modelCheck the device label, web interface, or administrative panel to verify the model number is WRH-733GBK or WRH-733GWHAffected if Device is either WRH-733GBK or WRH-733GWH model
-
Check if telnet function is enabledLog into the device administrative interface and navigate to the telnet or network services settings. Verify whether the telnet server or function is turned onAffected if Telnet function is enabled in the device configuration
-
Verify telnet port accessibilityPerform a port scan of the device from the network (e.g., nmap -p 23 <device_ip>) to determine if TCP port 23 (telnet) is open and reachableAffected if Telnet port (TCP 23) is open and accessible from untrusted networks
-
Check firmware versionIn the device administrative interface, locate the firmware version information (usually under Status, System, or Maintenance). Compare this to any vendor advisories or patches released for CVE-2025-43879Affected if Installed firmware version predates any vendor-released patch for this vulnerability
-
Inspect for indicators of compromiseReview device logs and network traffic for unusual telnet connections, unexpected shell commands, or evidence of command injection attempts (look for suspicious characters like ; | & $ in log entries)Affected if Logs show unexpected telnet connections or shell command patterns indicative of exploitation
A defender is affected if they own a WRH-733GBK or WRH-733GWH device with telnet enabled and accessible, especially on unpatched firmware versions.
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.
From vendor dataIf vendor patch unavailable, disable telnet function and implement network segmentation to limit exposure; monitor for Indicators of Compromise.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43879 — 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-43879 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