Skip to main content
Mallory
UnratedVulnerability

CVE-2021-35407: Unauthenticated Command Injection in Prolink PRC2402M mesh.cgi

Updated 7 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2021-35407CWE-78

CVE-2021-35407 is an unauthenticated OS command injection vulnerability in the Prolink PRC2402M router, observed on firmware version 20190909. The flaw is in the /cgi-bin/mesh.cgi CGI handler, specifically the code path reached when the page parameter is set to upgrade. In that path, the get_upgrade_page function reads attacker-controlled parameters including key from the HTTP query string, retrieves lan_ipaddr from NVRAM, and constructs a shell command using sprintf with the format string "echo -n '%s' | md5sum". Because the key parameter is not properly validated or sanitized before being incorporated into the command and executed via popen, an attacker can inject shell metacharacters and execute arbitrary commands. The vulnerable endpoint is reachable over HTTP GET and does not require authentication. Successful exploitation results in arbitrary command execution as root on the affected device.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote, unauthenticated attacker to execute arbitrary OS commands on the router with root privileges. This can lead to full device compromise, including modification of configuration, execution of follow-on payloads, persistence, interception or manipulation of network traffic, use of the device as a pivot point, and complete loss of integrity and confidentiality of the appliance.

Mitigation

If you can’t patch tonight, do this now.

Until patched firmware is deployed, restrict access to the router’s web management interface and CGI endpoints, especially from the WAN. Disable remote administration if not required, limit management access to trusted hosts or a dedicated management network, and use firewall or ACL controls to block external access to /cgi-bin/mesh.cgi. Monitor for suspicious requests to /cgi-bin/mesh.cgi with page=upgrade and anomalous shell metacharacters in query parameters such as key. Because exploitation is unauthenticated, exposure of the management interface materially increases risk.

Remediation

Patch, then assume compromise.

Apply the vendor fix released by Prolink. The disclosure timeline in the provided content indicates the issue was reported on 2021-06-10, an initial patch was bypassed on 2021-06-11, and the vulnerability was ultimately fixed on 2021-06-13. Upgrade affected PRC2402M devices to a firmware version containing the final fix. From a secure coding perspective, remediation requires eliminating shell invocation with unsanitized user input, avoiding sprintf-based command construction, and replacing popen-based shell execution with safer APIs and strict input validation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2021-35407 exploited in the wild?
As of Apr 11, 2026, Mallory has no reports of CVE-2021-35407 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-35407?
As of Apr 11, 2026, Mallory has found no public exploit for CVE-2021-35407.
Is there a patch for CVE-2021-35407?
Apply the vendor fix released by Prolink. The disclosure timeline in the provided content indicates the issue was reported on 2021-06-10, an initial patch was bypassed on 2021-06-11, and the vulnerability was ultimately fixed on 2021-06-13.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.