Skip to content
Fencer Intel
critical 9.8

CVE-2022-3218 in the critical feed json

Necta WiFi Mouse (Mouse Server) client-side authentication bypass

published 4y ago modified 4mo ago also EUVD-2022-42632

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
74.2%
EPSS 74.2% chance of exploitation in 30 days, percentile 99.4%
public exploits
1
Metasploit

Summary

Due to a reliance on client-side authentication, the WiFi Mouse (Mouse Server) from Necta LLC's authentication mechanism is trivially bypassed, which can result in remote code execution.

Patch / fix

Is CVE-2022-3218 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/misc/wifi_mouse_rce)
  2. Published

Exploit prediction

74.19% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/windows/misc/wifi_mouse_rce Wifi Mouse RCE metasploit exploit, normal rank, 2021-02-25
  • exploit-db.com https://www.exploit-db.com/exploits/50972 referenced PoC, tagged "exploit" by a source, unverified
  • exploit-db.com https://www.exploit-db.com/exploits/49601 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/H4rk3nz0/PenTesting/blob/main/Exploits/wifi%20mouse/wifi-mouse-server-rce.py referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/168509/WiFi-Mouse-1.8.3.4-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Necta LLC WiFi Mouse (Mouse Server)

Classification

Weakness
  • CWE-603 Use of Client-Side Authentication
  • CWE-287 Improper Authentication

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.