CVE-2022-47701
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 · uneditedCOMFAST (Shenzhen Sihai Zhonglian Network Technology Co., Ltd) CF-WR623N Router firmware V2.3.0.1 is vulnerable to Cross Site Scripting (XSS).
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 confidenceThe COMFAST CF-WR623N router firmware V2.3.0.1 contains a Cross Site Scripting (XSS) vulnerability. XSS vulnerabilities allow attackers to inject malicious scripts into web pages viewed by other users, potentially stealing session cookies, credentials, or performing actions on behalf of victims. The medium CVSS score indicates moderate exploitability and impact.
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= 2.3.0.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLocate the physical router or check network inventory for COMFAST CF-WR623N devices. The model number is typically printed on a label on the device bottom or back.Affected if The device is a COMFAST CF-WR623N router
-
Determine firmware versionAccess the router web interface (typically at 192.168.1.1 or 192.168.0.1), log in, and navigate to System Status or Firmware Upgrade page to view the installed firmware version. Alternatively, check the admin panel for a firmware version display.Affected if The displayed firmware version is exactly 2.3.0.1
-
Verify web interface accessibilityConfirm the router HTTP/HTTPS management interface is reachable on the local network. Try accessing the router IP address from a browser.Affected if The router web interface is accessible and responds to HTTP requests
-
Confirm XSS exposureThe vulnerability exists in the router web interface. If version 2.3.0.1 is running and the web interface is active, the XSS vulnerability is present in the login or configuration pages where user input is handled without proper sanitization.Affected if Firmware version 2.3.0.1 is installed AND the web management interface is active
You are affected if you have a COMFAST CF-WR623N router running firmware version 2.3.0.1 with the web management interface enabled.
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 dataContact COMFAST (Shenzhen Sihai Zhonglian Network Technology Co., Ltd) for an official firmware patch that addresses the XSS vulnerability. If no patch is available, implement input validation and output encoding on the router's web interface, or consider network segmentation to limit exposure.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47701 — 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-2022-47701 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