dbcve.org
Mf286r FirmwareOperating system · Zte

CVE-2022-39066

HIGH · 8.8 CVSS v3.1 Published 2022-11-22
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 SQL injection vulnerability in ZTE MF286R. Due to insufficient validation of the input parameters of the phonebook interface, an authenticated attacker could use the vulnerability to execute arbitrary SQL injection.

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 · moderate confidence

The ZTE MF286R router contains a SQL injection vulnerability in its phonebook interface. Due to insufficient input validation on parameters within this interface, an authenticated attacker can inject arbitrary SQL commands, potentially allowing data exfiltration or database manipulation.

MitigationImplement strict input validation and use parameterized queries (prepared statements) for all database interactions in the phonebook interface. Restrict administrative access to minimize the attack surface.

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:< mf286r_b07

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's web interface or check the device label to confirm the model is ZTE MF286R
    Affected if The device is not a ZTE MF286R router, then it is not affected by this CVE
  2. Check the firmware version
    Log into the router web interface and navigate to Status or Management > Firmware version, or check the version displayed in the web UI
    Affected if The firmware version is mf286r_b07 or higher, then the vulnerability is patched; if the version is before mf286r_b07 (e.g., b06, b05, etc.), the device is affected
  3. Verify the phonebook interface is accessible
    Navigate to the phonebook feature in the router web interface (usually under Phone Settings, Call Settings, or Contacts)
    Affected if The phonebook interface is not present or accessible, then the attack surface may not exist; if it exists and the device runs a vulnerable firmware version, the device is affected
  4. Confirm authentication status to the router
    Log into the router administration panel with administrative credentials
    Affected if The attacker already has valid credentials to access the router admin panel, they can exploit this SQL injection in the phonebook interface on vulnerable firmware versions

A user is affected if they have a ZTE MF286R router running firmware version mf286r_b06 or earlier, with the phonebook interface accessible and the attacker having valid administrative credentials to the router.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and use parameterized queries (prepared statements) for all database interactions in the phonebook interface. Restrict administrative access to minimize the attack surface.

Recommended fix High confidence

mf286r_b07 or later

  1. Log into the ZTE MF286R router administration interface
  2. Navigate to the firmware update or system maintenance section
  3. Download the firmware update mf286r_b07 or a later stable version from ZTE's official support portal (support.zte.com.cn)
  4. Upload the firmware file to the device and initiate the update process
  5. Wait for the device to reboot and apply the firmware
  6. After reboot, verify the firmware version has been updated to mf286r_b07 or later
  7. Confirm the phonebook interface is functioning normally

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

Fix this in Mf286r Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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