CVE-2022-40619 — Command Injection in Netgear R6230 Firmware
FunJSQ, 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 2.5% (30-day exploitation probability)+13
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Netgear R6230 Firmware, Netgear R6260 Firmware, Netgear R7000 Firmware…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Netgear | R6230 Firmware | < 1.1.0.112 | Vulnerable | NIST National Vulnerability Database |
| Netgear | R6260 Firmware | < 1.1.0.88 | Vulnerable | NIST National Vulnerability Database |
| Netgear | R7000 Firmware | < 1.0.11.134 | Vulnerable | NIST National Vulnerability Database |
| Netgear | R8900 Firmware | < 1.0.5.42 | Vulnerable | NIST National Vulnerability Database |
| Netgear | R9000 Firmware | < 1.0.5.42 | Vulnerable | NIST National Vulnerability Database |
| Netgear | Rax120 Firmware | < 1.2.8.40 | Vulnerable | NIST National Vulnerability Database |
| Netgear | Rax120v2 Firmware | < 1.2.8.40 | Vulnerable | NIST National Vulnerability Database |
| Netgear | Rbr20 Firmware | < 2.7.2.26 | Vulnerable | NIST National Vulnerability Database |
| Netgear | Rbs20 Firmware | < 2.7.2.26 | Vulnerable | NIST National Vulnerability Database |
| Netgear | Xr300 Firmware | < 1.0.3.72 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.7 | CVSS 3.1 | High | 2.2 | 5.5 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 7.7 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.54%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- CVSS changed · 7.7
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-9214 Improper Input Validation in Netgear R7000 Firmware Aug 11, 2026
- Medium CVE-2026-11738 Improper Input Validation in Netgear Be9300 Firmware Aug 11, 2026
- Medium CVE-2026-11814 Command Injection in Netgear Be9300 Firmware Aug 11, 2026
- Medium CVE-2026-11735 Stack-based Buffer Overflow in Netgear R7000 Firmware Aug 11, 2026
- Medium CVE-2026-9210 Certain NETGEAR routers allow authenticated administrators to gain unintended control of the router Jun 9, 2026
- High CVE-2026-9212 Insufficient authentication and input validation in certain NETGEAR products Jun 9, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-40619 is "Command Injection in Netgear R6230 Firmware", rated High. It affects R6230 Firmware (Netgear); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.7 describes technical severity. EPSS 2.54% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.