Skip to main content
Mallory
CriticalExploited in the wildCISA KEVVulnerability

CVE-2010-5330: Command Injection in Ubiquiti AirOS stainfo.cgi

Published Jun 11, 2019 · 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
EPSS40.2%99th percentile
CISA KEVYesAdded Apr 15, 2022
In the wildActivePer CISA KEV
Vendor
Ui
IdentifiersCVE-2010-5330CWE-77 · Improper Neutralization of Special…

CVE-2010-5330 is a command injection vulnerability affecting certain Ubiquiti devices running AirOS/AirSync firmware, including examples such as Nanostation5. The issue exists in the CGI endpoint stainfo.cgi (also referred to as 'Show AP info'), where the ifname parameter is not properly sanitized. An attacker can supply shell metacharacters in a crafted HTTP GET request, causing attacker-controlled commands to be interpreted by the underlying shell. The vulnerability is remotely reachable through the web interface on affected devices.

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 remote execution of arbitrary operating system commands on the affected device via the vulnerable web interface. This can lead to full compromise of the device, including unauthorized administrative actions, alteration of configuration, deployment of malware or botnet payloads, use of the device as a pivot or proxy, and disruption of network services provided by the device.

Mitigation

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

If immediate patching is not possible, restrict access to the device management interface so stainfo.cgi is not reachable from untrusted networks, especially the public Internet. Limit administrative access using network ACLs, VPN-only management, firewall rules, and segmentation. Monitor HTTP requests to the management interface for suspicious use of shell metacharacters in the ifname parameter and review devices for signs of compromise. Because this vulnerability has been listed by CISA as actively exploited, exposed devices should be prioritized for isolation or patching.

Remediation

Patch, then assume compromise.

Upgrade affected firmware to a fixed release. The provided fixed versions are v4.0.1 for 802.11 ISP products, v5.3.5 for AirMax ISP products, and v5.4.5 for AirSync firmware. Organizations should identify exposed and legacy Ubiquiti AirOS/AirSync devices and update them to the appropriate patched firmware version.

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
UiAirosoperating_system
FAQ

Frequently asked questions

Is CVE-2010-5330 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 15, 2022.
Is there a public exploit for CVE-2010-5330?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2010-5330.
Is there a patch for CVE-2010-5330?
Upgrade affected firmware to a fixed release. The provided fixed versions are v4.0.1 for 802.11 ISP products, v5.3.5 for AirMax ISP products, and v5.4.5 for AirSync firmware.
What products are affected by CVE-2010-5330?
Ui Airos.
How severe is CVE-2010-5330?
CVE-2010-5330 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 40.2% (99th percentile) as of Oct 16, 2026.
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.