Which versions of Wa300 are affected by CVE-2026-4497?

An unauthenticated remote code execution vulnerability affecting Totolink WA300 routers allows attackers to take complete control of affected devices without credentials.

Is there a public PoC exploit available for CVE-2026-4497?

Yes, a public proof-of-concept exploit is available for CVE-2026-4497. Prioritise patching immediately. EPSS: 1.9%.

How to fix or mitigate CVE-2026-4497?

Within 24 hours: Identify all Totolik WA300 devices in inventory and isolate affected units from production networks if possible; create an incident response plan. Within 7 days: Implement network segmentation to restrict router administrative access, deploy monitoring for suspicious command patterns, and contact Totolink support for patch availability timeline. Within 30 days: Develop a device replacement or firmware upgrade plan once patches are released; consider alternative router models as interim solution if business continuity permits.

Wa300 CVE-2026-4497

Q: What is the CVSS score of CVE-2026-4497?

CVE-2026-4497 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 1.9%.

EUVD-2026-13770 MEDIUM

OS Command Injection (CWE-78)

2026-03-20 VulDB

Command Injection Wa300 TOTOLINK

5.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Apr 29, 2026 - 01:11 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

PoC Detected

Apr 03, 2026 - 11:31 vuln.today

Public exploit code

EUVD ID Assigned

Mar 20, 2026 - 19:15 euvd

EUVD-2026-13770

Analysis Generated

Mar 20, 2026 - 19:15 vuln.today

CVE Published

Mar 20, 2026 - 19:02 nvd

MEDIUM 6.9

DescriptionCVE.org

A vulnerability was determined in Totolink WA300 5.2cu.7112_B20190227. Affected by this issue is the function recvUpgradeNewFw of the file /cgi-bin/cstecgi.cgi. This manipulation causes os command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.

AnalysisAI

A critical OS command injection vulnerability exists in Totolink WA300 router firmware version 5.2cu.7112_B20190227, specifically in the recvUpgradeNewFw function within /cgi-bin/cstecgi.cgi. An unauthenticated remote attacker can exploit this flaw to execute arbitrary operating system commands on the affected device. A public proof-of-concept exploit has been released on GitHub, significantly lowering the barrier to exploitation and increasing real-world risk.

Technical ContextAI

This vulnerability affects the Totolink WA300 wireless access point (CPE: cpe:2.3:a:totolink:wa300), a consumer networking device. The root cause is CWE-78 (OS Command Injection), where user-supplied input to the recvUpgradeNewFw function in the /cgi-bin/cstecgi.cgi CGI script is not properly sanitized before being passed to system shell commands. This is a common vulnerability pattern in embedded device firmware where developer-implemented CGI scripts handle firmware upgrade operations without adequate input validation. The vulnerability exists in the web management interface, allowing network-accessible exploitation without prior authentication.

RemediationAI

Users should immediately check the Totolink vendor website at https://www.totolink.net/ for updated firmware versions that address this command injection vulnerability and upgrade to the latest available firmware for the WA300 model. Until patching is feasible, implement network-level mitigations by restricting administrative access to the device management interface to trusted IP addresses only, disabling remote management features if not required, and placing the device behind a firewall that blocks external access to the web interface on ports 80 and 443. Consider replacing the device with a more actively maintained alternative if Totlink has not released security updates, as the presence of a public exploit (https://github.com/user-attachments/files/25790616/Unauthenticated.Remote.Code.Execution.in.TOTOLINK.WA300.via.Command.Injection.in.recvUpgradeNewFw.zip) makes continued use without patches extremely risky.