dbcve.org
Cf Wr623n FirmwareOperating system · Comfast Project

CVE-2022-47700

HIGH · 7.5 CVSS v3.1 Published 2023-01-31
Fix available
A fix is available. Upgrade to after 2.3.0.1 or later.
See remediation →
84/100
Remediation priority · High
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
COMFAST (Shenzhen Sihai Zhonglian Network Technology Co., Ltd) CF-WR623N Router firmware V2.3.0.1 and before is vulnerable to Incorrect Access Control. Improper authentication allows requests to be made to back-end scripts without a valid session or authentication.

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

The COMFAST CF-WR623N router firmware versions 2.3.0.1 and before contains an incorrect access control vulnerability in its web management interface. The vulnerability allows unauthenticated attackers to directly access back-end scripts without requiring any valid session or authentication credentials. This represents a complete authentication bypass that could enable attackers to gain administrative control of the device.

MitigationUpgrade the router firmware to a version beyond V2.3.0.1 that patches this authentication bypass vulnerability; if no patched firmware is available, disable remote web management and restrict access to the management interface via firewall rules.

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
Cf Wr623n FirmwareOperating system
Affected:<= 2.3.0.1

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 router model and firmware version
    Log into the router web management interface (typically at 192.168.1.1 or 192.168.0.1) and navigate to System Status or Firmware Version page. Alternatively, check the physical device label or use commands like 'nvram get firmware_version' if you have telnet/ssh access.
    Affected if The firmware version displayed is 2.3.0.1 or lower.
  2. Confirm web management interface is enabled
    Navigate to the router's admin panel and check the Remote Management or Web Management settings (usually under Security or Administration sections). Verify if the HTTP/HTTPS management interface is turned on.
    Affected if The web management interface is enabled and accessible.
  3. Test for unauthenticated access to back-end scripts
    From a browser or using curl, attempt to access common back-end script paths without providing any login credentials. Try URLs such as http://[router-ip]/cgi-bin/luci or similar endpoints that should normally require authentication.
    Affected if The back-end scripts respond without redirecting to a login page or returning an authentication error.
  4. Check if remote (WAN) web management is enabled
    In the router admin interface, look for settings labeled 'Remote Management', 'WEB Management', or 'Access from WAN' in the Security or Administration sections. Note the allowed IP range if remote access is permitted.
    Affected if Remote web management is enabled and the router is accessible from the WAN side on HTTP/HTTPS ports.

You are affected if your COMFAST CF-WR623N router runs firmware version 2.3.0.1 or lower AND the web management interface is accessible (especially from WAN), allowing unauthenticated access to back-end scripts.

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
Upgrade available Upgrade to a release after 2.3.0.1
Interim mitigation

Upgrade the router firmware to a version beyond V2.3.0.1 that patches this authentication bypass vulnerability; if no patched firmware is available, disable remote web management and restrict access to the management interface via firewall rules.

Fix this in Cf Wr623n Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

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