dbcve.org
Mf286r FirmwareOperating system · Zte

CVE-2023-25649

HIGH · 8.8 CVSS v3.1 Published 2023-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
There is a command injection vulnerability in a mobile internet product of ZTE. Due to insufficient validation of SET_DEVICE_LED interface parameter, an authenticated attacker could use the vulnerability to execute arbitrary commands.

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

Command injection vulnerability in ZTE mobile internet product's SET_DEVICE_LED interface due to insufficient parameter validation, allowing authenticated attackers to execute arbitrary OS commands on the affected device.

MitigationImplement strict input validation and sanitization on the SET_DEVICE_LED interface parameters; use parameterized queries or safe API functions to prevent command injection rather than passing unsanitized input to system calls.

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
Mf286r FirmwareOperating system
Affected:= cr_lvwrgbmf286rv1.0.0b04

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 the device model
    Access the router web interface or CLI and locate the device model information, typically found in the Status, System Info, or Device Info page. The affected model is ZTE MF286r.
    Affected if The device is NOT a ZTE MF286r router - if so, this CVE does not apply.
  2. Check the installed firmware version
    In the router web interface, navigate to Management, Firmware Upgrade, or Status page to view the firmware version. Alternatively, access the CLI via telnet/ssh and run commands like 'cat /etc/version' or 'version' to display firmware information.
    Affected if The firmware version is NOT exactly cr_lvwrgbmf286rv1.0.0b04 - only this specific version is affected.
  3. Verify the web management interface is accessible
    Attempt to access the router's web interface by entering the device IP address in a web browser. Confirm the login page loads and the interface is reachable on the network.
    Affected if The web interface is NOT accessible - the attacker would need network access to exploit this vulnerability.
  4. Confirm the SET_DEVICE_LED interface exists
    This requires examining the router's web application endpoints. If you have access to the firmware image or can proxy web requests, look for the SET_DEVICE_LED function call in the web interface's API or CGI-bin files.
    Affected if The SET_DEVICE_LED interface does NOT exist or is NOT enabled on the device.
  5. Assess authentication exposure
    Determine if valid credentials for the router admin interface are known or guessable. Check if default credentials are in use, or if the device allows remote management that could be accessed.
    Affected if You have NOT obtained valid administrator credentials to the device - authentication is required for exploitation.

You are affected only if you are running exactly firmware version cr_lvwrgbmf286rv1.0.0b04 on a ZTE MF286r router AND the SET_DEVICE_LED interface is accessible with valid admin credentials.

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

Implement strict input validation and sanitization on the SET_DEVICE_LED interface parameters; use parameterized queries or safe API functions to prevent command injection rather than passing unsanitized input to system calls.

Fix this in Mf286r Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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