Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2022-28912: Command Injection in TOTOLink N600R /setting/setUpgradeFW

Published May 10, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS2.5%85th percentile
CISA KEVNoNot listed
In the wildReported16 exploitation records in Mallory
Vendor
Totolink
IdentifiersCVE-2022-28912CWE-78 · Improper Neutralization of Special…

CVE-2022-28912 is a command injection vulnerability in TOTOLink N600R firmware version V5.3c.7159_B20190425. The issue was reported in the /setting/setUpgradeFW endpoint, where the filename parameter is insufficiently sanitized before being used in a context that allows execution of operating system commands. An attacker able to reach this functionality can supply a crafted filename value to inject arbitrary shell commands, resulting in command execution on the 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 can allow arbitrary command execution on the affected router. Depending on the privileges of the vulnerable process, this may enable full compromise of the device, including modification of configuration, installation of persistent backdoors, interception or redirection of network traffic, and use of the router as a pivot point for further attacks within the local network.

Mitigation

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

Restrict access to the router management interface, especially the firmware upgrade functionality, to trusted administrative networks only. Disable remote administration from untrusted networks or the Internet. Enforce strong administrative credentials, segment management access, and monitor for unexpected configuration changes or command execution artifacts. As an interim measure, prevent exposure of the web administration interface until patched firmware is deployed.

Remediation

Patch, then assume compromise.

Upgrade to a fixed firmware version from TOTOLink if one is available. The vulnerable code handling the filename parameter in /setting/setUpgradeFW should be corrected to avoid passing user-controlled input to shell command contexts, using strict input validation and safe APIs that do not invoke the shell. If vendor remediation information is not available, replacement of the affected firmware or device may be necessary.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
TotolinkN600r Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2022-28912 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-28912?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-28912.
Is there a patch for CVE-2022-28912?
Upgrade to a fixed firmware version from TOTOLink if one is available. The vulnerable code handling the filename parameter in /setting/setUpgradeFW should be corrected to avoid passing user-controlled input to shell command contexts, using strict input validation and safe APIs that do not invoke the shell.
What products are affected by CVE-2022-28912?
Totolink N600r Firmware.
How severe is CVE-2022-28912?
CVE-2022-28912 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.5% (85th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.