Wr 1200 FirmwareOperating system · Greenpacket

CVE-2023-26866

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
GreenPacket OH736's WR-1200 Indoor Unit, OT-235 with firmware versions M-IDU-1.6.0.3_V1.1 and MH-46360-2.0.3-R5-GP respectively are vulnerable to remote command injection. Commands are executed using pre-login execution and executed with root privileges allowing complete takeover.

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

Remote command injection vulnerability in GreenPacket OH736 WR-1200 Indoor Unit and OT-235 devices allowing pre-authentication OS command execution with root privileges, enabling complete device takeover.

MitigationApply vendor firmware updates M-IDU-1.6.0.3_V1.1 and MH-46360-2.0.3-R5-GP; if unavailable, disable network exposure or isolate affected devices and implement network segmentation as compensating controls.

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
Wr 1200 FirmwareOperating system
Affected:= m-idu-1.6.0.3_v1.1
Ot 235 FirmwareOperating system
Affected:= m-idu-1.6.0.3_v1.1= mh-46360-2.0.3-r5-gp

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.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 checks

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

  1. Identify device model
    Locate the physical device or log into the management interface to confirm the model is GreenPacket OH736 WR-1200 Indoor Unit or OT-235
    Affected if Device model is either WR-1200 or OT-235
  2. Check firmware version
    Access the device web interface or CLI and navigate to the firmware/version information page. Compare the installed firmware version against the affected versions: m-idu-1.6.0.3_v1.1 or mh-46360-2.0.3-r5-gp
    Affected if Firmware version exactly matches m-idu-1.6.0.3_v1.1 or mh-46360-2.0.3-r5-gp
  3. Verify web management interface exposure
    Determine if the device web management interface is accessible from the network. Check router/firewall configurations for port 80/443 or any custom HTTP port forwarding to the device
    Affected if Web management interface is exposed to network without network segmentation or access controls
  4. Check for unauthorized processes or connections
    If you have CLI or SSH access to the device, run commands to list active processes (ps) and network connections (netstat) to identify any unexpected outbound connections or unknown processes
    Affected if Unexpected processes running or suspicious outbound connections to unknown IPs are present
  5. Review web server logs for command injection patterns
    If accessible, examine the device web server logs for patterns indicating command injection attempts, such as semicolons, pipe symbols, or backticks in URL parameters
    Affected if Log entries show command injection patterns in HTTP requests

The device is affected if it is a GreenPacket WR-1200 or OT-235 running firmware version m-idu-1.6.0.3_v1.1 or mh-46360-2.0.3-r5-gp, and its web management interface is network-accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates M-IDU-1.6.0.3_V1.1 and MH-46360-2.0.3-R5-GP; if unavailable, disable network exposure or isolate affected devices and implement network segmentation as compensating controls.

Fix this in Wr 1200 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26866 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26866 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