Threats / Ubiquiti / CVE-2010-5330
CVE-2010-5330
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Ubiquiti AirOS vulnerability
Ubiquiti AirOS devices are vulnerable to command injection through stainfo.cgi GET requests, allowing unauthenticated remote code execution.
Verdict
Today item — known-exploited.
A command injection flaw in Ubiquiti AirOS enables attackers to execute arbitrary commands on affected devices via crafted GET requests. The vulnerability has been exploited in the wild and poses significant risk to wireless infrastructure deployments.
CISA KEV Yes · 2022-04-154EPSS 0.34641 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-15).
Probability (EPSS)
EPSS 0.34641 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Ubiquiti, AirOS. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1039 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious GET request to stainfo.cgi containing shell metacharacters to break out of the intended command context.
Business
Wireless access points and bridges become compromised entry points into enterprise or service provider networks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary system commands with the privileges of the web server process running on the device.
Business
Attackers gain persistent control over network infrastructure, enabling lateral movement and data exfiltration.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify device configuration, install backdoors, or redirect traffic through the compromised equipment.
Business
Network availability is degraded, customer trust erodes, and regulatory compliance obligations are breached.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05