CVE-2022-40619
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 · uneditedFunJSQ, a third-party module integrated on some NETGEAR routers and Orbi WiFi Systems, exposes an HTTP server over the LAN interface of affected devices. This interface is vulnerable to unauthenticated arbitrary command injection through the funjsq_access_token parameter. This affects R6230 before 1.1.0.112, R6260 before 1.1.0.88, R7000 before 1.0.11.134, R8900 before 1.0.5.42, R9000 before 1.0.5.42, and XR300 before 1.0.3.72 and Orbi RBR20 before 2.7.2.26, RBR50 before 2.7.4.26, RBS20 before 2.7.2.26, and RBS50 before 2.7.4.26.
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 analysisUser input reaches a command interpreter without being fully separated from the command itself, so an attacker can append instructions of their own. Because those run with the application's privileges, it frequently means control of the host. The lasting fix is to avoid constructing commands from input — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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.7.2.26< 1.1.0.112< 1.1.0.88< 1.0.11.134< 1.0.5.42< 1.0.5.42< 1.2.8.40< 1.2.8.40CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
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 · scoped1.0.5.421.0.11.1341.1.0.88
Upgrade to RBR20 firmware 2.7.2.26 or later; R6230 firmware 1.1.0.112 or later; R6260 firmware 1.1.0.88 or later; R7000 firmware 1.0.11.134 or later; R8900 firmware 1.0.5.42 or later; R9000 firmware 1.0.5.42 or later; Rax120 firmware 1.2.8.40 or later; Rax120v2 firmware 1.2.8.40 or later; XR300 firm
- Identify the exact NETGEAR router or Orbi model number from the affected list (R6230, R6260, R7000, R8900, R9000, Rax120, Rax120v2, RBR20, XR300, RBR50, RBS20, or RBS50)
- Access the router's web interface by entering the router's LAN IP address in a web browser
- Navigate to the Administration or Settings section and locate the Firmware Update option
- Check the current firmware version under Router Info or similar (affected if below: RBR20 < 2.7.2.26, R6230 < 1.1.0.112, R6260 < 1.1.0.88, R7000 < 1.0.11.134, R8900 < 1.0.5.42, R9000 < 1.0.5.42, Rax120 < 1.2.8.40, Rax120v2 < 1.2.8.40, XR300 < 1.0.3.72, RBR50 < 2.7.4.26, RBS20 < 2.7.2.26, RBS50 < 2.7.4.26)
- Download the latest firmware from the official NETGEAR support website (kb.netgear.com) for the specific model
- Upload the firmware file through the router's web interface and allow the upgrade to complete
- After reboot, verify the firmware version has been updated to the fixed release
- If available, disable or uninstall the FunJSQ feature if not needed to reduce attack surface
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40619 — 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-40619 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