CVE-2022-40623

CVE-2022-40623 is a high-severity vulnerability in Wavlink Wn531g3 Firmware with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

The WAVLINK Quantum D4G (WN531G3) running firmware version M31G3.V5030.200325 does not utilize anti-CSRF tokens, which, when combined with other issues (such as CVE-2022-35518), can lead to remote, unauthenticated command execution.

Frequently asked questions

What is CVE-2022-40623?
The WAVLINK Quantum D4G (WN531G3) running firmware version M31G3.V5030.200325 does not utilize anti-CSRF tokens, which, when combined with other issues (such as CVE-2022-35518), can lead to remote, unauthenticated command execution.
How severe is CVE-2022-40623?
CVE-2022-40623 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-40623 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-40623?
CVE-2022-40623 affects Wavlink Wn531g3 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-40623?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-40623 published?
CVE-2022-40623 was published on 2022-09-13 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Wavlink Wn531g3 Firmware

All CVEs affecting Wavlink Wn531g3 Firmware →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →